New metaphor of filesystem
I am thinking of doing this for my final year project.
I propose to design a new filesystem (or patch existing ones) that supports the concepts of "virtual folders". Virtual folders can be nested, but mostly i won't be like that. Each 'virtual folder' has a vname. Each file/folder in classic filesystem can be attached one or more vnames. Hence they will be visible when one of the corresponding 'virtual folder' is opened by user.
I was just reading about SFS in short time. So my questions is this feasible to implement in linux. That is, are they any gotchas that I need to worry about when implementing such thing over VFS?
Or could I do this in the user-space level? I have heard of user-space filesystem layer for linux. Can I use that with operation like updating into database? (which itself is quite non-responsive)
Please throw some thoughts.
PS: Anybody know whether seth's storage is actively developed?
I propose to design a new filesystem (or patch existing ones) that supports the concepts of "virtual folders". Virtual folders can be nested, but mostly i won't be like that. Each 'virtual folder' has a vname. Each file/folder in classic filesystem can be attached one or more vnames. Hence they will be visible when one of the corresponding 'virtual folder' is opened by user.
I was just reading about SFS in short time. So my questions is this feasible to implement in linux. That is, are they any gotchas that I need to worry about when implementing such thing over VFS?
Or could I do this in the user-space level? I have heard of user-space filesystem layer for linux. Can I use that with operation like updating into database? (which itself is quite non-responsive)
Please throw some thoughts.
PS: Anybody know whether seth's storage is actively developed?
