Red Hat Bugzilla – Bug 435976
RFE: anaconda should use a mirrored repo on a hard drive
Last modified: 2008-03-31 21:00:19 EDT
Description of problem:
When you select an install source as a local hard drive, anaconda only expect to
find a MS-DoS filesystem with an iso image in it. This prevents the use of
Everything directories that exist in an ext3 file system on a USB hard drive.
Version-Release number of selected component (if applicable):
As late as anaconda-220.127.116.11
Steps to Reproduce:
1. start an install with a rescue cd
2. tell anaconda you want to install from a hard drive (USB, PATA, SATA...)
Anaconda indicates it can not find install media.
Anaconda works with the directory structure it finds, as if it had nfs mounted
it from a server.
extra credit, also allow it to use the updates/$releasever/$basearch/ directory
which is also on the hard drive.
Not saying that this shouldn't be changed, but afaik the requirement to have a
directory full of ISOs for a "hard disk" type install has existed for a long
time (at least back as far as RHL8/RHEL3 - I think since this install type was
You're not actually limited to msdos for holding the isos.
But the reason that the requirement is for the ISOs and not the tree is that we
actually used to allow the tree, but people would inevitably only have partial
mirrors of what they thought mattered and installs would fail. After a few
years of these bugs, we cut our losses and also reduced the testing matrix a
bit. So not really interested in adding it back and making things worse again
Thats why this is an RFE=Request For Enhancement.
and I be not the only one:
Yes jigdo and isoinfo help, but why should I have to build a DVD image when I
have the correct stuff right there on the hard drive.
Re Comment #2
So you never have folks reporting problems with the NFS mounted file systems?
Yes, this comes up from time to time. But the amount of requests is very very
low in comparison to the amount of effort required for maintaining another path
through the installer. And while there's a very occasional such report with
NFS, they're far rarer -- I suspect due to the higher barrier to entry keeping
out people who are more likely to do things that are unwise.
I had occasion to wish for this feature. I only have one x86_64 machine and
wanted to use buildinstall to build a new set of images on that machine and then
use them to install in another partition. (netinst.iso didn't work and I thought
rebuilding it might use a slightly more recent version of anaconda.) It seems
silly to have to go to an extra step (making an iso file that will end up being
loop mounted to get back the original structure) or copying the images back to
another machine so that they can be used for a url install.
While this is not a high priority, it is something that might help people with
only one local machine participate in rawhide testing.
As far as the broken trees goes, I think that is a separate problem. My guess
would be that people aren't skimping on getting the trees, but probably they are
dealing with out of sync mirrors. Even the fedoraproject mirror has partial
updates regularly. I have learned to check the time stamps to make sure that the
images, repo meta data and packages all appear to be in sync. There might be
things that the project could do to cut down on this. Perhaps the master could
be doing directory renames (if it isn't) instead of copying over updates.
I understand the increased complexity in Anaconda, but I have also wanted to have this option available.
I'm wondering why the installer failing causes any more issue than trying to debug network installs that
fail? The same outputs would end up on virtual terminals (can't find file xxx, etc). Wouldn't it be possible
to install from local harddrive, with files, only if there is repo metadata present? That would at least
remove alot of the issue with half-complete mirrors right? (essentially, a network install with a local
It would be perfectly acceptable to insist on metadata; a particular use for
this is test installs of rawhide, where doing it every day might be considered
prohibitive via the usual make-an-iso route not just because of the cost of DVD
blanks, but for the time involved.
(in other words, why can this not be supported only within rawhide, or with an
option like "iamanext4developer" ;o))
Funny, I have patches to make this work.
And proof that it works, note the boot line at the top:
If this does not make it into anaconda proper, I could maintain this setup if
there is interest and someone could host the initrd.img for me.