Subject: Re: devfs, was Re: ptyfs fully working now...
To: Christos Zoulas <firstname.lastname@example.org>
From: Pavel Cahyna <email@example.com>
Date: 11/13/2004 16:30:46
On Sat, 13 Nov 2004 08:30:43 +0000, Christos Zoulas wrote:
> On Nov 13, 12:10am, firstname.lastname@example.org (Bill Studenmund) wrote:
> -- Subject: Re: devfs, was Re: ptyfs fully working now...
> | I like the idea of a file that contains info about modes and owners, and I
> | hadn't thought about whiteouts - good idea. However I think a better way
> | to do this is a binary database. I think the keys should be locators;
> | where the device is in the config hierarchy. For each entry, we keep most
> | of the info you have below - name, uid, gid, mode (or ACL), mtime, atime,
> | ctime (I don't think birthtime matters as it won't show up in stat), and
> | type.
> Fine, I agree that the device mapping should be using locators.
If such scheme would effectively allow to "wire down" device names without a
kernel recompile, that would be great. But be sure to include the device
names as one of the values held in the entry, because all the programs
(think newfs, fsck, mount, cdrecord, and things like mtools for disks, for
other devices e.g. getty, lpd, pppd, apcupsd...) use device names (here I
mean filenames in /dev). So it would make no sense if, after devices have
moved, permissions were set correctly, but such programs used another device
because the the names changed.
Thanks and bye Pavel