[KLUG Members] New advances in filesystems.

[Adam Williams]

> > Very interesting stuff!
> >   http://cda.mrs.umn.edu/~mine0057/fs.pdf
> Very interesting, although I'm puzzled they don't mention resource forks
> which do much of the same things, and filesystems like XFS which offer
> basically openended meta data (attributes, properties), etc...
> The ability to put real constraints on file system objects is very cool.
> But some of the things he suggests (enviroment in a filesystem, etc...)
> seem a bit obtuse - I mean, why?

"Setuid and setgrp need to go away. If Apache needs port 80, I should be
able to say  the apache user gets read and write access to port 80  to
the OS. If a process needs a capability, that capability should be
expressible as a file so that an access control list can be applied to
it."

It should be noted that this "capability" support already exists,
although not used by default in most distro's.  Technically apache does
not need to start as root to get port 80 - today, with no filesystem
magic.  

Every possible TCP/UDP port as a file?  I thought /dev was ugly enough
already.

There are some REALLY cool ideas here, but taken to far I think this all
gets really unmanageable.