Comment How stupid... (Score 1) 341
I switched to Redhat 4.2 way back when because its drivers were more up-to-date than the other distributions I had tried. Since then, I've had problems with 5.0 and 5.2. Bug fix RPMs have been posted, but I've recently run into three very different machines on which 5.2 (as shipped) would not install at all. However, I kludged a patched CDROM that works on all three. (Basic idea: Replace the original RPMs with symlinks to replacement RPMs -- excluding kernel RPMs which would cause LILO to fail at the end.)
I could post the scripts I use to generate the disks (starting from a RH 5.2 disk and a directory of patch RPMs), but with 6.0 only a few weeks away (hopefully including all the patches plus linux 2.2.3 plus GNOME 1.x), there's probably not much of a point.
Can anyone point me to TFM so I can R about how the lists of RPMs are *supposed* to be changed for Redhat CDROMs -- instead of using symlinks as I did? No doubt there will be patches for 6.0, and it can save a lot of installation time (or in some cases, make installation *possible*) to simply have the latest patches on the CDROM directly.
Thanks in advance,
Chuck Phillips
c d p @ p e a k p e a k . c o m . n o s p a m
I could post the scripts I use to generate the disks (starting from a RH 5.2 disk and a directory of patch RPMs), but with 6.0 only a few weeks away (hopefully including all the patches plus linux 2.2.3 plus GNOME 1.x), there's probably not much of a point.
Can anyone point me to TFM so I can R about how the lists of RPMs are *supposed* to be changed for Redhat CDROMs -- instead of using symlinks as I did? No doubt there will be patches for 6.0, and it can save a lot of installation time (or in some cases, make installation *possible*) to simply have the latest patches on the CDROM directly.
Thanks in advance,
Chuck Phillips
c d p @ p e a k p e a k . c o m . n o s p a m
