From: "Mike Watson" <mikew@xxxxxxxxxx>
> On Sunday 05 October 2003 10:47 pm, jdow wrote:
> > From: "Chuck Wolber" <chuckw@xxxxxxxxxxxxxxxx>
> >
> > > > > I have this same problem with 2.4.20 on RH8. Is there anyway
> > > > > to remove a FS label? That appears to be the problem.
> > > >
> > > > The program 'e2label' is just what you're looking for.
> > >
> > > Or go old skool:
> > >
> > > tune2fs -L label-name /dev/hdX
> >
> > "Logically" if the fstab "LABEL=/" does not work with devfs then some
> > translation process is not taking place correctly. That means the
> > disk label MAY mean nothing. If its presence guarantees a
> > mistranslation then the only help is "e2label <path to device>" to
> > create a blank or empty label. If you figure out what the form is for
> > <path to device> simply use that in fstab and be done with it.
> >
> > I wonder if this is somehow related to having the wrong mod-utils
> > with the kernel package.
> >
> > {^_^} I also admit, I don't guarantee the logic above. There could
> > be a fatal issue with devfs that means you just aren't going
> > to boot using devfs the way you want.
>
> The parameters for e2lable is
> e2label <device> <label>
>
> If no 2nd parameter is furnished, e2label returns the value of the
> existing label. So how do you specific a blank label?
Normally that is an exercise left to the newby. But I'll be nice.
e2label <device> ""
That is an empty label which should be the same as no label.
{^_^}
