Linked by Thom Holwerda on Sat 23rd Aug 2008 15:37 UTC
Editorial Earlier this week, we ran a story on GoboLinux, and the distribution's effort to replace the Filesystem Hierarchy Standard with a more pleasant, human-readable, and logical design. A lot of people liked the idea of modernising/replacing the FHS, but just as many people were against doing so. Valid arguments were presented both ways, but in this article, I would like to focus on a common sentiment that came forward in that discussion: normal users shouldn't see the FHS, and advanced users are smart enough to figure out how the FHS works.
Permalink for comment 327836
To read all comments associated with this story, please click here.
RE: Relation and Abstraction
by ari-free on Sun 24th Aug 2008 17:19 UTC in reply to "Relation and Abstraction"
ari-free
Member since:
2007-01-22

"I'm sure this isn't my idea, but perhaps it's time to dump the directory tree altogether and replace it with a relational database"

This was actually tried in an early version of BeOS:
http://www.letterp.com/~dbg/practical-file-system-design.pdf

"At the time, the BeOS managed extra information about files (e.g., header fields from an email message) in a separate database that existed independently of the underlying hierarchical file system (the old file system, or OFS for short). The original design of the separate database and file system was done partially out of a desire to keep as much code in user space as possible. However, with the database separate from the file system, keeping the two in sync proved problematic. Moreover, moving into the realm of general purpose computing brought with it the desire to support other file systems (such as ISO-9660, the CD-ROM file system), but there was no provision for
that in the original I/O architecture."

Edited 2008-08-24 17:19 UTC

Reply Parent Score: 2