OSDev.org

Hello, i'm a C coder!
I ask for your help .... i need information about developing a file system.I would appreciate some links to tutorials ....because i don't have a cc to buy books online.
Thank you!

Go to Google and type in the file system you want to use (ex. FAT...) and you will find a lot of resources and information.

Also check the ".:QuickLinkz:. <-- read this before you post" topic, you'll find there some links to wanted information

http://www.flipcode.com/tutorials/tut_vfs01.shtml
http://www.bell-labs.com/history/unix/tutorial.html

may interrest you. Many people consider it's better to stick on an existing filesystem (for compatibility with other systems/tools and because a bug in a filesystem can lead to severe data losses that end-user are unlikely to accept)

You may also google for the BeOS "practical-file-system-design.pdf" which is a free online eBook that explains everything needed to understand BeOS filesystem, or the article about NTFS by Andrew Tanenbaum

As a last piece of advice, if you want some idea of what an unconventional document system might look like, see Project Xanadu and the related Abora, Udanax, and ZigZag systems. For some historical perspective on these, there is also the Sunless Sea Cyberarchaeology Project (currently down, but should be available again soon), which archives much of the early debates among the Xanadu Project team members.

i'm working on a study project witch aims to develop a unixfs-like file systam, I will post it here when it'll be finished (after 2 or 3 weeks).
you can give me your mail so i can send it to you directly

I will place here the advantages and disadvantages of an own file system and an existing file system.

Advantage own file system:
- you design it
- you could specially fit it in your OS design.

Disadvantage:
- you have to write formatting software for ir
- special tools has to be made.

Advantage of an existing file system:
- you don't have to design it, a lot faster.
- you don't have to write the formatting software, and no special tools has to be made.

Disadvantages:

- there could be limitations.
- and you must follow the specs of the FS, and an FS could change.

Hope that I cleared out a BIT

hi,
Check this site. It has everything you need.
http://www.nondot.org/sabre/os/articles
http://www.nondot.org/sabre/os/articles/FileSystems/

But i prefer using the existing filesystems if developing own operating system.

regards.

Well, I'm not sure whether I choose an existing file system or an own filesystem.
If I'd choose for an existing filesystem, I'd take ReiserFS, I think (when I get the specs of the file system), if not I'd choose for my own file system

there are nice docs about ReiserFS on Reiser's project homepage ...

all i can find for now is http://www.cs.wisc.edu/~hochhaus/adsl-u ... serfs.html

Pype.Clicker wrote: there are nice docs about ReiserFS on Reiser's project homepage ...

all i can find for now is http://www.cs.wisc.edu/~hochhaus/adsl-u ... serfs.html

I read it, but it's too difficult explained, or is it just me ?
Other suggestions ?
Well, I THINK I'm going to start my own FS

well, ReiserFS is certainly *not* easy to understand because it uses quite advanced concepts. Make sure you correctly got what B+tree files are before you start reading more on Reiser itself.

Well, just going for my own FS
ReiserFS is too difficult, and ext2/3 is too standard, as so for FAT12/16/32

the final choice is up to you, but imho, studying Reiser or NTFS is one of the best way to prepare a *good* FS from your own design.

Pype.Clicker wrote: the final choice is up to you, but imho, studying Reiser or NTFS is one of the best way to prepare a *good* FS from your own design.

I can only agree, having exactly that base to build from. Except that I've not read reiserfs design as good as I should've...

Dennis, not using something because it is complex is a bad idea. Learn all there is to learn, ask questions (yes, my signature does mean something), and figure out the best way, not the not-too-hard way.