On 16 May 2001, Kai Henningsen wrote:
> hpa@transmeta.com (H. Peter Anvin) wrote on 15.05.01 in <3B01A044.F72BFDD1@transmeta.com>:
>
> > Personally, I would also like to see network devices manifest in the
> > filesystem namespace like everything else.
>
> Yes.
>
> Can we have a meta-rule?
>
> *Every* by-name kernel interface should have a filesystem variant.
>
> That is, if there's a kernel interface where you give the kernel a string
> to identify an in-kernel object, there should be some place in the file
> system (after mounting any prerequisites) that will respond to a path
> ending in that name.
You'll get in trouble with that in exactly one case: filesystem types.
No, it would make a lot of sense to have them as fs objects. For one
thing, we could turn mount(2) into
open appropriate fs type
convince the sucker that you are allowed, tell which device you want,
etc.
open mountpoint
mount(fs_fd, dir_fd)
Would work like charm, especially since we could fit the network filesystems
into the same scheme and get rid of the kludges a-la ncpfs mount sequence.
There's only one sore spot: how'd you mount _that_ fs? ;-)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed May 23 2001 - 21:00:15 EST