Re: Larger dev_t

Alexander Viro
2001-03-28T04:24:38Z

On 27 Mar 2001, Johan Kullstam wrote:

> it might be a mostly userspace solvable problem. a device daemon
> could create new devices on the fly, only they'd be ordinary
> filesystem devices. for example it might be better to hack ls to not
> show dormant devices. a cronjob could call a grim device reaper to
> cull nodes not used for a long time...

Why the hell do we have to reinvent every wheel out there? Especially
when we _already_ have that wheel... You don't need to hack ls in order
to deal with "dormant" entries. That's what autofs is for. Doing that
quite fine, thank you very much. Furrfu...

> what do other vaguely unix-like systems do? does, say, plan9 have a
> better way of dealing with all this?

Plan9 doesn't have devfs. You can say
bind -a #f /dev
and that gives you /dev/fd[0-3]{disk,ctl}. I.e. /dev is a union of
device filesystems you've mounted (bound, actually) there. Combined
with autofs (and replacing bind #f with mount -t devfloppy) it's
pretty much what we could use.

Think of devpts - it's the same kind of beast. As for putting stuff into
/etc/fstab - not funny. /etc/auto_dev would do just fine, especially
if /etc/fstab would contain the minimal (==permanent) subset. Nothing stops
you from examining /lib/modules/ and updating /etc/auto_dev from rc scripts
upon boot.