If I add C-shell style $var:t support, then you will be able to do
this easily in the config file. Of course, hacking devfsd.c is another
option (possibly better: I'll get back to you on that one).
> > It's cleaner than tarring up /dev, and it's persistent. Ideally it would
> > record changes you make with chown and chmod in a database, but you could
> > probably instrument that yourself (simply hook the change event to call a
> > script which writes the perms in a coherent way, and then optional_include that
> > at the top of devfsd.conf)
>
> > Quite frankly, I thought this argument had died out ages ago.
>
> With no resolution!
>
> It's a butt-ugly kludge that falls on its ass and dies any
> time the system fails to shut down properly or if you have transient
> devices. One of the big things with 2.4 is improved resource
> management. We should now expect something reasonable from hot
> swapable devices and PCMCIA and Firewire and USB. The tar option
> blows goats when you factor transient devices into the equation.
> The devfsd option is marginally better but doesn't support
> everthing, can't be configured to support everything, and still
> leaves timing windows like buckshot.
OK, will people *PLEASE* stop whinging about this? I've already said,
multiple times, that I'll be adding "tunnelling" down to the
underlying disc-based FS. It's Work In Progress (there's even evidence
of it in fs/devfs/base.c)
Just be patient, and it will be solved cleanly.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/