On Thu, 2003-07-24 at 08:16, Leonard den Ottolander wrote: > Yeah, but I think you already compared the two images and came to the > conclusion that they are identical. In that case creating a ramdisk by > hand does not solve anything. O yes, I did suggest you edited linuxrc > in the ramdisk to get some debug info. Some commands to get some info > on the state of the machine during startup, and probably some sleep's > to study / write down the info before it scrolls by.
Since the system is remote, I'm not sure how to do that without looking at the syslogs. > But this editing > you can do on the original ramdisk. And yes, you can just re-gzip it. > If you edit it a lot it might get somewhat bigger due to the fact that > dirty unused sectors/bytes are still available in the image, but for > this purpose that is probably not a big problem. No problem. I'll see what happens with editing the linuxrc script. > You should definitely file a bug at http://bugzilla.redhat.com . It's > reproducible, and that way you might get the attention of a developer > that might actually solve your problem. Maybe the problem has already > been reported and somebody might have entered a workaround. Check it > out. Correction, there was a really stupid error on my part on the VMware machine, which was resolved when I upgraded -everything- correctly. I double checked, and it works on the VMware machine just fine. I had forgotten to upgrade all needed RPM's besides kernel. :| I made sure I didn't make the same mistake on the production box, but it still doesn't work. > Yup. RAID1 controllers are quite cheap, but when running RAID5 the > software solution does save quite some money (on hardware that is). The box I'm using only has room for one PCI card, which is taken up by the second NIC. :\ -- Ricky Boone <[EMAIL PROTECTED]> Planetfurry.com -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
