Description of problem:
When using loop back mounts of ISO images for http/ftp install, the installer
adds an extra element to the directory.
Version-Release number of selected component (if applicable):
Loop back mount the ISO images.
Begin the installer by booting from floppy and using the network driver disk as
Point the installer to the http/ftp site and use RHbeta as base dir.
The installer begins and goes through configuration.
When the installer prepares to get the packages from the http/ftp site, it
adds an extra element to the path.
The installer should begin looking in the same directory that the 2nd stage
installer was found.
This can be worked around by unmounting the ISO images and remounting in the
disc1 subdirectory after the installer fails to find the first package.
What directory are you pointing at to do your install (should be RHbeta/ and
then the disc1, disc2, disc3 will be checked automagically)
I am pointing it to RHbeta/. The second stage install is pulled from the
ftp/http site and runs. I go through the entire install configuration screens
(ie. partitioning, network setup, root password, package selection).
When the installer tries to find the first package to install (glibc-common), it
fails saying that it couldn't find the package.
Looking at one of the Alt-F consoles during the http install, it fails trying to
If I unmount the ISO images and remount under disc1, I can click OK and the
install finds and installs the packages.
Fixed in CVS, update disk is at http://people.redhat.com/~katzj/severn-updates.img.
If you place this as RedHat/base/updates.img, then it will get used and you
should be able to verify the fix.
I added the update.img to the RedHat/base directory but it didn't fix the problem.
Should I be able to loop back mount the img file? I get the following message
when I try:
Jul 23 23:16:24 system kernel: EXT2-fs: loop(7,0): couldn't mount because of un
supported optional features (20000).
I noticed the same message on the system that I am using for the beta.
*** Bug 101523 has been marked as a duplicate of this bug. ***
Mass-closing lots of old bugs which are in MODIFIED (and thus presumed to be
fixed). If any of these are still a problem, please reopen or file a new bug
against the release which they're occurring in so they can be properly tracked.