> In order to keep with the Unix frame of mind, a solution would be to
> build up a file system, for instance /net, which would
> automatically build up server information on different protocols. So
> the directory tree would look like:
>
> /net/
> smb/
> server1/
> fileservice
>
> I think this is a very neat idea (it's not mine). What do you think?
Maybe...
> In order to implement this, I see three options:
>
> 1.) It is implemented completely in the kernel.
> 2.) It is implemented minimally, making use
> of user space programs to retrieve information (userfs?).
2a.) Podfuk: hack midnight commander to know this filesystem and then
use hacked rpc.nfsd to export this filesystem to kernel. Basically
same as userfs except that portable and no kernel modification
needed. I believe this is the way to go. Take a look at
http://atrey.karlin.mff.cuni.cz/~pavel/podfuk/podfuk.html.
> I suspect that other network file systems could be added to this
> scenario. Does NFS and CODA broadcast server information?
I do not think so. NFS is not broken protocol, so it better should not
do such thing.
> Input would be greatly appreciated.
-- I'm really pavel@atrey.karlin.mff.cuni.cz. Pavel Look at http://atrey.karlin.mff.cuni.cz/~pavel/ ;-).- 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.altern.org/andrebalsa/doc/lkml-faq.html