[Top] [All Lists]

Re: labels resolved (was Re: XFS volume labels)

To: Ed McKenzie <eem12@xxxxxxxxxxx>
Subject: Re: labels resolved (was Re: XFS volume labels)
From: Russell Cattelan <cattelan@xxxxxxxxxxx>
Date: Thu, 05 Apr 2001 13:58:54 -0400
Cc: Russel Ingram <ringram@xxxxxxxxxxxxxx>, Nathan Scott <nathans@xxxxxxxxxxxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx
References: <Pine.LNX.4.30.0104051013270.1756-100000@localhost.localdomain> <986492703.10964.0.camel@eem12.resnet.cornell.edu>
Sender: owner-linux-xfs@xxxxxxxxxxx
Ed McKenzie wrote:

> Russel,
> I had already done this, and it didn't work. I encountered a similar
> issue before, and worked out with rgooch that it was a devfsd bug. That
> was awhile back, so this may be a different issue entirely, but I'm
> waiting for his reply on this one.
> Agreed, though, that devfs (and esp. devfsd) need work in the
> documentation department.
> Further discussion off-list ... we're way offtopic now :)

Actually any info that helps us ship devfs less painfully is welcome.

If devfsd.config needs fixing then we can do that before the
next rpm release.

> -ed
> On 05 Apr 2001 10:28:47 -0600, Russel Ingram suggested:
> >             The one mentioned here can actually be resolved by watching
> > the /var/log/messages for the name of the resource the kernel is looking
> > for when it loads that module, then use that resource name as an alias to
> > the proper module in /etc/modules.conf.  That much will make the module
> > load properly.  Past that it's just a matter of telling devfsd to make
> > the correct symbolic link to the device file that your software is looking
> > for at the same time it makes the new format device file.

Russell Cattelan
Digital Elves inc. -- Currently on loan to SGI
Linux XFS core developer.

<Prev in Thread] Current Thread [Next in Thread>