[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Mon, 20 May 2002 19:42:12 +0200
On Mon, May 20, 2002 at 10:20:27AM -0700, Thomas Bushnell, BSG wrote:
> > Have you thought about writing a translator for /dev itself, rather than
> > using a script to populate a directory? devfs the Hurd way.
> Certainly we have. I think this is ultimately the Right Thing, in
I've just wondered myself about it, but I am not sure how this would be done
best. The good thing about having one node per device file is that you can
set permissions and ownership etc for each node seperately, persistent
across reboots. I would not want to miss that.
So, what you do is you have a special translator on /dev. What does it do?
Does it provide a virtual filesystem hierarchy, a bit like the mux
filesystems do, or would it be more like fakeroot translator, passing most
accesses through, but catching lookups of non-existing nodes, and creating
missing device files on the fly?
The former would have to store the file metadata elsewhere.
`Rhubarb is no Egyptian god.' Debian http://www.debian.org email@example.com
Marcus Brinkmann GNU http://www.gnu.org firstname.lastname@example.org
- /dev translator,
Marcus Brinkmann <=