, but I am not sure how this would be
> > done best.
>
> Something I would like is complete autodetection of hardware. It'd be
> cool if a /dev translator could read /usr/share/discover/pci.lst (or
> whatever) and add subnodes with translators for those devices.
>
> Alterna
directory? devfs the Hurd way.
> >
> > Certainly we have. I think this is ultimately the Right Thing, in
> > fact.
>
> I've just wondered myself about it, but I am not sure how this would be
> done best.
Something I would like is complete autodetection of hardware. It'd
Marcus Brinkmann <[EMAIL PROTECTED]> writes:
> 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 catc
One idea we have discussed in the past is a translator that supports one
(or perhaps more) virtual directory of virtual nodes that can have all the
per-node information but no file contents. i.e., the permissions, uid/gid,
and translator for each node would be stored, e.g. in a db file.
___
On Mon, May 20, 2002 at 10:20:27AM -0700, Thomas Bushnell, BSG wrote:
Someone 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, i
