Hello and mi first question

naiksidd_85 · Post by **naiksidd_85** » Thu Feb 21, 2008 10:59 pm

not to offend any one but i will be more than happy if you help me create a FS by dinner......
I am struggling hard for it.

and yes after that Dinner will be on me.

zaleschiemilgabriel · Post by **zaleschiemilgabriel** » Fri Feb 22, 2008 5:11 am

naiksidd_85 wrote:not to offend any one but i will be more than happy if you help me create a FS by dinner......
I am struggling hard for it.

and yes after that Dinner will be on me.

If that's a joke, I don't get it. Also, if it is a joke, stop reading here (or goto next_paragraph

).
If by "help me create" you mean "help me code" you're s**t out of luck. If you meant "help me design" that sounds a little better.

I for one have read the SFS spec and I like it. Although it does have it's flaws (it's more suitable for flash drives than IDEs) and there are parts I don't agree with, it's the best I've read so far and by far different to anything I might have though up. Cheers to the authors!
I'm glad there's even a way to access it in Windows. That's an extra cheers.

When I get home I'll give VDisk a try and if it works the way I expect it to, I'm on my way to implementing SFS.

Unrelated question: When you see something like "reserved (must be 0)" in a specification, what do you interpret it like:
a. The field it describes must be set to 0 when it is created (the first time it is written)
b. The field must be checked when the entire structure is read and if it is not 0, the whole structure should be considered to be incompatible (or broken)
c. same as above, but only give a warning and continue
d. what else could it mean?

JamesM · Post by **JamesM** » Fri Feb 22, 2008 7:01 am

If that's a joke, I don't get it.

I believe the post above yours was referring to the post (not by you) which said that a filesystem was extremely easy to design.

Unrelated question: When you see something like "reserved (must be 0)" in a specification, what do you interpret it like:

If I'm writing data which includes one of those fields, I would set it to zero. If reading data (and possibly editing then writing again), I would use whatever value is already there, to enable upwards compatibility.