Re: (Semi-random) thoughts on device tree structure and devfs

[Masao Uebayashi <uebayasi%gmail.com@localhost>]

On Fri, Mar 12, 2010 at 5:09 AM, der Mouse 
<mouse%rodents-montreal.org@localhost> wrote:
>>> This could also enable you to do
>>>   mount -t devfs /etc/devfs-bindchroot.db /var/chroot/bind/dev
>>> for example.
>
>> I don't think a static database will cut it.  What happens when
>> someone attaches a new USB stick and devfs generates a bunch of new
>> nodes?  What ownership and permissions should they get?
>
> Presumably the database holds, among other things, information
> specifying whether new nodes will appear in such a case, and, if so,
> what ownership and modes they'll have.

My (current) idea is to expose all devices as perm 0000, then let
devfs promote those nodes.  As joerg said, this is kind of mtree(8),
in that:

- it should use well-established syntax
- it calls mknod(2) internally

It's not like mtree(8) in that:

- it can't hard-code paths.

We'll probably end up with some patterns, but let's not re-invent a new syntax.

Masao