Advanced Operating Systems
M4: File System
The SOS file system features a flat directory structure, containing files and
the terminal device
You will need to maintain file descriptors containing a present read position in the file. This requires some minimal process descriptor block (PCB) data structure. Again, you will need to modify this structure as you go on, so do not waste too much time on the full details right now. You may wish to initially only deal with a single client process, data on which is kept in a single PCB variable. This avoids dealing with process IDs for the time being.
The low-level file system is implemented by the NFS file system on your host machine. You are provided with an NFS client library for accessing files on your host Linux machine. Once again, it is your responsibility to understand the working of the provided code.
IP stack and NFS
In the code you are provided with a
Apart from the initialisation and mounting filesystems, the NFS library provides an asynchronous interface, which means when you call the function, you must also provide a callback function which will be called when the transaction is completed. This should make it easy to provide a blocking interface each clients, without blocking the whole system.
The NFS server you will be talking to is your host machine. The filesytem
you mount is
One of the major issues you will need to deal with in this milestone is
converting an asynchronous interface (as provided by
If you are planning on doing the file system caching, or dynamic file system advanced component you should probably consider them in your design now.
You must have some test code to demonstrates that you have implemented the
As always you should be able to explain any design decisions you made, specifically, the design of your open file table and how you dealt with the asynchronous/synchronous problem.
Last modified: 27 Jul 2006.