file system servers
Posted: Sat Sep 04, 2004 3:28 pm
Hi,
Instead of the all-is-file paradigm, would it be very efficient to write userland drivers mapping devices (soundcards, video, storage) to files? That way I could have legacy support for code which operate that way but I could use other ideas in the primary drivers.
I am thinking of having a virtual file system as a userland server and I'm actually almost ready to start coding but- I have no clue how such basic funcionality as mkdir, delete file can be achieved ;D I mean how a file system driver exports these functions? Because the open, read, write are all exported in a pointer table. But the mkdir, erase are not.
I heard someone talking 'bout "inodes" in the context of file services. I think I should know what it is before I write a vfs
What other considerations do you find important here?
Cheers,
~Adrian
Instead of the all-is-file paradigm, would it be very efficient to write userland drivers mapping devices (soundcards, video, storage) to files? That way I could have legacy support for code which operate that way but I could use other ideas in the primary drivers.
I am thinking of having a virtual file system as a userland server and I'm actually almost ready to start coding but- I have no clue how such basic funcionality as mkdir, delete file can be achieved ;D I mean how a file system driver exports these functions? Because the open, read, write are all exported in a pointer table. But the mkdir, erase are not.
I heard someone talking 'bout "inodes" in the context of file services. I think I should know what it is before I write a vfs
What other considerations do you find important here?
Cheers,
~Adrian