xfs
[Top] [All Lists]

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

To: cattelan@xxxxxxxxxxx
Subject: Re: labels resolved (was Re: XFS volume labels)
From: Ed McKenzie <eem12@xxxxxxxxxxx>
Date: Thu, 5 Apr 2001 02:00:44 -0400
Cc: Nathan Scott <nathans@xxxxxxxxxxxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <dlcr8z87yce.wl@xxxxxxxxxxxxxxxxxxxxx>; from cattelan@xxxxxxxxxxx on Wed, Apr 04, 2001 at 11:41:05PM -0500
References: <200104041856.f34IueT02232@xxxxxxxxxxxxxxxxxxxx> <20010404183337.A2201@xxxxxxxxxxxxxxxxxxxxxxxx> <10104050910.ZM24677@xxxxxxxxxxxxxxxxxxxxxxxx> <20010404200725.A2571@xxxxxxxxxxxxxxxxxxxxxxxx> <10104051109.ZM24598@xxxxxxxxxxxxxxxxxxxxxxxx> <20010404211834.A3164@xxxxxxxxxxxxxxxxxxxxxxxx> <10104051126.ZM24497@xxxxxxxxxxxxxxxxxxxxxxxx> <20010404214505.A1212@xxxxxxxxxxxxxxxxxxxxxxxx> <10104051206.ZM25020@xxxxxxxxxxxxxxxxxxxxxxxx> <dlcr8z87yce.wl@xxxxxxxxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Wed, Apr 04, 2001 at 11:41:05PM -0500, cattelan@xxxxxxxxxxx wrote:
> Other than the "/dev/mouse doesn't exist" or "/dev/cdrom doesn't
> exist" what other problems have you experienced? 

My biggest problem is that devfs completely breaks module
load-on-open. I have XFree86 set up to run on matroxfb, and with devfs
enabled, its attempt to open /dev/fb0 returns ENOENT or some such
instead of modprobing matroxfb_base. fb0 is an "old" name, sure, but
there's nothing in /dev/fb to link to even if devfsd were that smart.

Likewise, if I don't load my SCSI driver in initrd, I can't open
/dev/scd0 and expect it to load initio.o automatically. cdrecord just
comes back and says it can't find a CD writer.

> So yes devfs will remain turned on unless significant problems are
> encountered.

Well, I like devfs a whole lot more than a vat of mknod spawn, but it
still has implementation issues that need to be fixed.

-- 
Ed McKenzie
<eem12@xxxxxxxxxxx>

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