Well I reinstalled FC1 last night and I did not reproduce the "bug". Sometimes my memory isn't as good as I think it is. I should have listened to Vince and duplicated the bug before I put in a report. No harm done and I have really learned allot.
Wayne you were right. I don't remember doing it but I must have passed the second root= option to grub in the advanced boot options section of the install. That's pretty much the only explanation. And one more thing to set the record straight. The root=LABEL=/ did save me from crashing on the first install. The second entry must have been ignored. For me this was a pretty confusing problem I created. I didn't know why the machine booted with the wrong root= statement. When I commented out the initrd line I got the same type of error as when I used the wrong root= statement. They both said something about an image statement or initrd. Well even though the bug wasn't a bug the list still did it's job. Which is help me figure out where I screwed up! -Cody -----Original Message----- From: Taylor Cody L. Contr 502 AOS/PETS Sent: Wednesday, May 12, 2004 1:32 PM To: 'Linux/Unix Advocates/Users Hawaiian community discussion list' Subject: RE: [LUAU] FC1 Well unless I added root=/dev/hdc3 during install and forgot about it, Fedora did it on it's own. I didn't notice / had been placed on hdc5 until after I recompiled my kernel, copied and modified the grub entry and rebooted. Of course I got a kernel panic. The first time I modified a root= entry manually in grub was once I discovered / was on hdc5. The root=LABEL=/ statement didn't save me from crashing because I left it in place on the original kernel entry and removed the initrd line and I got the same kernel panic as when I recompiled my kernel. Im convinced the initrd line is the only reason I didn't get a kernel panic with the original grub.conf. Im going to reinstall FC1 tonight to try and reproduce the suspected bug. And not to worry I will not re-install over existing partitions.
