I've had a workstation install with gnome + kde + games selected crash on
me with a message that it couldn't find xxgdb-<bla>.rpm, which is correct
since this is on disk2.
After doing a select individual packages unselect xxgdb, I got the same error
for yp-tools. Now I all of a sudden get a feeling that this is related to me
doing a network install.
I assume that the network installer assumes that it is installing from an
filesystem containing the complete RedHat dir, not just disc1 may I point out
that this is BAD, since I can now no longer export the CD, but instead need
around 1 gig of hd-space to be able todo an network install, or do some ugly
stuff with links.
You are correct you need to have both discs available if you are selecting
a package set containing RPMS from both. This is due to the large size
of what comes with a Linux distribution these days.
Yes, nice, but as I already said, this is BAD, I for example use network
installs for both my laptops, and for one of my 2 main test systems, also my
alpha needs todo a network install sometimes due to a broken installer. This
means that I need a lott of free disk space which I don't have. I also know a
lott of other people used to directly nfs exporting the cd-rom, that isn't
possible this way.
I strongly urge RedHat to concider adding an option to allow exporting the CD
again, like asking for an nfs mount-point for disc2, or to replace the disk when
a disc2 rpm is not found.
(What about disk1 disk2 files, which tell the installer which disk(s) are in
It might seem silly to ask someone to exchange a disk during a network install,
but trust me it isn't.
All network installs I've done have always been form an exported cd.