On Wed, 2007-06-13 at 21:07 +0100, Sharpe, Sam J wrote:
> On 13 Jun 2007, at 20:53, Tom Sightler wrote:
> 
> > On Wed, 2007-06-13 at 15:11 -0400, Kendrick Hernandez wrote:
> >> On our RHEL4 tester we put in the symlink manually, but also had to
> >> modify grub.conf so that "root=" parameter on the kernel line  
> >> pointed to
> >> the root device instead of "LABEL=/"; otherwise the symlink was  
> >> removed
> >> and /dev/root recreated after reboot. I've tried this also on the  
> >> RHEL5
> >> box, to no avail, unfortunately.
> >
> > Sure enough, I finally found a RHEL4 system which used "LABEL=/" in
> > grub.conf and it does indeed have the restrictive /dev/root device  
> > node
> > rather than the symbolic link to the actual device.  It just so  
> > happens
> > that practically all of our RHEL4 systems have either LVM paths or
> > physical partitions on the root= line.
> 
> Ahhh... LABEL=/ is default RHEL behaviour I believe... (at least my  
> kickstart looks vanilla and I don't see us changing it anywhere) you  
> must have foreseen this problem in advance and pre-prepared your  
> systems by using LVM or direct device paths ;o)

I'd love to take credit for that, but it wouldn't explain why I miss so
many other Redhat bugs that bite us now and then.  I actually think the
systems using direct device paths may very well be systems that were
upgraded from RHEL3 and, before that, RHEL2.1.  Was LABEL=/ the default
for RHEL3/2.1?

I'm pretty sure all fresh installs of RHEL4 were LVM but we never really
used LVM on earlier releases.

> Not that the problem bothers me on the systems I have installed - we  
> don't use Amanda *and* we don't backup /dev anyway... I guess the fix  
> for the OP is to change grub to point to a physical device, the  
> downside being you are affected by changes in device ordering.

It doesn't bother me either, we don't use Amanda or backup dev.  I don't
think the fix works on RHEL5, only for RHEL4, but a quick workaround
would be to just add the appropriate commands to rc.local to change the
permissions as required.

Later,
Tom


_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list

Reply via email to