If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Comment

The Linux kernel team simply isn't interested in Reiser for the reasons we all know. It's not a matter if it's a good filesystem or not, it's just that there aren't developers willing to enter the "reiser" world.

My 2 cent marketing suggestion for Reiserfs: rename the filesystem to a new name, wait like 2 years so that everyone learns the new name and forgets about "reiser's" history. This is the only chance to get over the political reasons that is blocking Reiser.

Comment

The only thing that interests me about Reiser4 are the things that were promised but never happened: accessing files as directories and using this interface as a standard way of managing metadata, putting different permissions on each line/field of /etc/passwd, all the stuff that was in the "future vision" whitepaper.

Without those features what makes Reiser4 more compelling than Btrfs?

Comment

The only thing that interests me about Reiser4 are the things that were promised but never happened: accessing files as directories and using this interface as a standard way of managing metadata, putting different permissions on each line/field of /etc/passwd, all the stuff that was in the "future vision" whitepaper.

Without those features what makes Reiser4 more compelling than Btrfs?

The former isn't particularly useful, easier implementation of this would be to extend nautilus, which already has the ability to display file metadata -- just needs to be modified to ALTER that metadata, which is a fairly simple task.

The latter can be accomplished by switching to a database instead of using /etc/passwd. I can't see any particularly compelling reason to build your filesystem around a specific file.

Comment

The former isn't particularly useful, easier implementation of this would be to extend nautilus, which already has the ability to display file metadata -- just needs to be modified to ALTER that metadata, which is a fairly simple task.

The latter can be accomplished by switching to a database instead of using /etc/passwd. I can't see any particularly compelling reason to build your filesystem around a specific file.

The entire point of doing all this in the filesystem was to be able to access and manipulate metadata with standard unix tools - anything that understands files and directories. Instead of metadata being application-specific it would be universal. Obviously the /etc/passwd example was not the only possible use for that feature.