True, I haven't tried MacOS X, but not for lack of wanting to. I'm eagerly awaiting the release.
However...
This author obviously doesn't have a clue about what the Be File System is because the BFS attempts to solve some of the problems he talks about.
"A file should be allowed to have no name, one name or many names. Many files should be allowed to share one name. A file should be allowed to be in no directory, one directory, or many directories. Many files should be allowed to share one directory. Of these eight possibilities, only three are legal and the other five are banned -- for no good reason."
With symlinks a file can be allowed to have one name or many names. With symlinks a file can be allowed to be in one directory or many directories. With the BFS a file can be allowed to have "no name" if the attributes of the file are what's important.
There is a huge untapped potential for the BFS for proprietary systems and file management.
Slashdot Mirror
True, I haven't tried MacOS X, but not for lack of wanting to. I'm eagerly awaiting the release.
However...
This author obviously doesn't have a clue about what the Be File System is because the BFS attempts to solve some of the problems he talks about.
"A file should be allowed to have no name, one name or many names. Many files should be allowed to share one name. A file should be allowed to
be in no directory, one directory, or many directories. Many files should be allowed to share one directory. Of these eight possibilities, only three are legal and the other five are banned -- for no good reason."
With symlinks a file can be allowed to have one name or many names. With symlinks a file can be allowed to be in one directory or many directories. With the BFS a file can be allowed to have "no name" if the attributes of the file are what's important.
There is a huge untapped potential for the BFS for proprietary systems and file management.