WFS, my FS design

piranha · Post by **piranha** » Mon Mar 17, 2008 6:58 pm

So, I started writing a FS design in school after a test, and I typed it up when I got home:

Thoughts?

-JL

Ninjarider · Post by **Ninjarider** » Mon Mar 17, 2008 8:45 pm

not sure what you want your end results to be. have you thought about user priv. somthing that unix has. the ablility for the creater to set global group and user priviliges.

piranha · Post by **piranha** » Mon Mar 17, 2008 10:06 pm

I mostly just want to have the simplest FS possible.

-JL

Combuster · Post by **Combuster** » Tue Mar 18, 2008 1:37 am

I mostly just want to have the simplest FS possible.

Use SFS in that case. It has pretty much the same design but doesn't suffer from several limits your design imposes.

JackScott · Post by **JackScott** » Tue Mar 18, 2008 1:43 am

It also has a prewritten driver/utility for Windows, and there are several other OS projects using it.

Ready4Dis · Post by **Ready4Dis** » Tue Mar 18, 2008 5:48 am

Or, just support Fat, it's very simple to understand and write drivers for, and as a benefit, you can read/write to it under windows, linux, mac, beos, and many other things. I just don't see the point of creating your own BASIC file system when plenty exist that are documented and supported (like, how do you check your disk for consistancy unless you write a utility). When I was writing my Fat formatting utlities, I would run chkdsk on it to see if there were any problems, then i could copy a file using windows or dos, and see what the difference was with my code vs. what happened when doing it via windows/dos.

piranha · Post by **piranha** » Tue Mar 18, 2008 8:21 am

I will eventually support fat, but for now I don't need to.

As a question of learning, What limitations?

-JL

Combuster · Post by **Combuster** » Tue Mar 18, 2008 3:45 pm

- 32-bit filesizes
- 8-bit (!) file offsets
- filenames hardlimited to 55 characters
and by far not complete enough to write an implementation (or for detecting more subtle flaws)