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."
Permalink for comment 216211
To read all comments associated with this story, please click here.
Why?
by Alwin on Sat 24th Feb 2007 22:13 UTC
Alwin
Member since:
2005-07-17

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 this guy is a driving force behind rewriting the core of an operating system. Work that requires experience, insight (foresight, if you will), and in general: solid coding skills. There are very few people that can do what this guy can, AND have the time/desire to work on this particular project.

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

Helloooo! There are so many to choose from... Most of them decently engineered, debugged and mature. What does he *really* need that *no* existing filesystem provides? If so, why not pick what comes closest, and add [desired feature] to it?

Come on Matt, don't get sidetracked, don't waste your time on stuff that can be done later, or by others. Don't you want DragonFly to be a solid OS first, before spending time on [desired feature #xyz] ?

Reply Score: 5