Linked by Thom Holwerda on Sat 24th Feb 2007 21:25 UTC, submitted by mdoverkil
BSD and Darwin derivatives Apparently, Matt Dillion has decided to roll his own filesystem for DragonFly. "Here is my initial outline of the filesystem design. It is open for discussion. Please feel to ask questions for anything you do not understand. I do not intend to start coding anything for at least two weeks. There are currently two rough spots in the design. First, how to handle segment overflows in a multi-master environment. Such overflows can occur when the individual masters or slaves have different historical data retention policies. Second, where to store the regeneratable indexes."
Thread beginning with comment 216801
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Why?
by twenex on Tue 27th Feb 2007 04:40 UTC in reply to "Why?"
Member since:

This is too silly for words... I mean, it is well known that the real limitation in OSS projects is the available amount of menpower (number of people that have the skills to do the job, and time to work on it).

And how is that not "a real limitation" in non-OSS projects?

In fact I'd say that the really successful OSS projects make more progress than the really successful closed-source projects.

And then, instead of focussing on the groundwork, this guy says: "I need a new filesystem!".

In what way are filesystems "not groundwork"? If you develop an OS w/o a filesystem, what are you going to store your data on - a cheese sandwich?

Reply Parent Score: 2