Messages in this thread | | | From | Hans Reiser <> | Date | Wed, 30 Jun 1999 23:28:01 +0000 (/etc/localtime) | Subject | Re: Summary of how linux can best avoid the need for streams |
| |
I am not opposed to putting filters in userspace.
Hans
Pavel Machek writes: > Hi! > > > I am not saying put an FS into a file, I am saying make the filesystem > > effective enough that nobody needs to create things like structured > > storage. Given that as a goal, what is needed? > > > > I propose the following: > ... > > * filters, such that "dirname/..tar" generates a tar file when read, and > > "dirname/..cat" concatenates for read, and "filename/..filtername" runs > > filtername on the file/directory filename. > > How do you want to implement such filters? You certainly do not want > them in kernel? > > If you want them in userspace, just use coda + podfuk > (http://atrey.karlin.mff.cuni.cz/~pavel/podfuk/podfuk.html). I believe > podfuk is right way for things like dirname#tar creating tar file from > the directory. (I've got it working.) > > It provides additional goodies like /#ftp:sunsite/ etc. > > I think podfuk is pretty nice proof that filters do not need to be in > kernel... Is there any reason not to use coda trick? [podfuk is not > neccesseraliry ideal piece of code, but concept works.] > > Pavel > -- > I'm really pavel@ucw.cz. Look at http://195.113.31.123/~pavel. Pavel > Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
- 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.tux.org/lkml/
| |