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 216404
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: plan9
by fithisux on Sun 25th Feb 2007 16:29 UTC in reply to "RE: plan9"
Member since:

May I ask some foolish questions?

1. Couldn't DF implement the Plan9 filesystem?
2. Couldn't DF evolve to a logical continuation of Plan9? 3. Is it possible without rewritting everything?
4. What are the candidate filesystems instead or writing another one?

Thanks for your answers.

Reply Parent Score: 1

RE[3]: plan9
by Cloudy on Sun 25th Feb 2007 23:22 in reply to "RE[2]: plan9"
Cloudy Member since:

They're not foolish questions, but the answer always comes down to "In theory yes, but Matt won't."

I've known Matt for 10 or 12 years now; since he was at Best inc and I was using it as an ISP. Once he has decided that a piece of software should be a certain way there is no changing his mind.

He's got a certain model of scalable distributed computing in mind. Dragonfly will meet that model and it's not Plan 9's.

Reply Parent Score: 3