I have to run Red Hat Enterprise Linux AS release 4 (Nahant Update 4) on
a customer project. This is, as far as I know, the newest stable Red Hat
Enterprise Release.

The most important command on this system is "chroot /debian".

The redhat system was installed with as many default values as possible
(also lvm configuration). 
Because I want to be able, to also boot debian directly, I used the
patch described below.

Here is the requested symlink info:

ls -l /dev/VolGroup00/LogVol00 
lrwxrwxrwx  1 root root 31 Dec 15 00:44 /dev/VolGroup00/LogVol00 ->
/dev/mapper/VolGroup00-LogVol00

ls -l /dev/mapper/VolGroup00-LogVol00 
brw-rw----  1 root disk 253, 0 Dec 15 01:43
/dev/mapper/VolGroup00-LogVol00

If this is a to specific change request, do you see a possiblity to have
a config file, with additional LVM naming schemas?


> -----Original Message-----
> From: maximilian attems [mailto:[EMAIL PROTECTED] 
> Sent: Freitag, Dezember 15, 2006 00:46
> To: Schumacher, Bernd; [EMAIL PROTECTED]
> Subject: Re: Bug#402931: initramfs-tools does not support 
> redhat lvm naming schema
> 
> On Wed, 13 Dec 2006, Schumacher, Bernd wrote:
> 
> > Subject: does not support redhat lvm naming schema
> > Package: initramfs-tools
> > Version: 0.85c
> > Severity: wishlist
> > Tags: patch
> 
> ok.
>  
> > -- start patch for 
> /usr/share/initramfs-tools/scripts/local-top/lvm --
> > --- lvm.org 2006-12-08 12:32:28.000000000 +0100
> > +++ lvm     2006-12-08 12:43:36.000000000 +0100
> > @@ -35,6 +35,11 @@
> >             vgchange -ay
> >             exit 0
> >             ;;
> > +        # Support redhat naming scheme
> > +   /dev/VolGroup*)
> > +           vgchange -ay
> > +           exit 0
> > +           ;;
> >     esac
> >  
> >     # Make sure that we have a d-m path
> > -- end patch for /usr/share/initramfs-tools/scripts/local-top/lvm --
> 
> can you add some explation to your patch?
> some motivation why this naming was chosen or how is it 
> guided is that a /dev/VolGroup/Lv symlink?
> does latest FC still use that one?
> 
> --
> maks
> 

Reply via email to