## File System Team

#### Team Leader: Cleo Saulnier

#### Members

1. Sean Heacock
2. Mike Currington
3. Timo Flink
4. Nick Marrone
5. John McCarthy
6. Josh Shepard
7. John Orrange
8. Doug Peterson

### Basic Overview

The File System team is dedicated to designing and implementing the proprietary File System of EOS. Currently only the design has been completed, although the implementation is in progress. The main goal of this group is to enable the use of multiple File Systems in a seamless fashion within EOS. Because of the limitations of DOS, a proprietary File System has been designed to overcome these limitations. But with the possibility of multiple File Systems, you'll still be able to access your DOS (or other File System) drives.

The current design of the EOS File System is very similar to that of UNIX, except that no blocks are set aside for i-nodes, as this would limit the number of files allowed and wastes storage when not in use.

As well, variations on the current File System are currently being worked on to make disk access faster.

And finally, since Hard Drives and Floppy Drives, etc... are devices, this team will often need to coordinate efforts with the Device Driver Team.

### In the Works

There are still many things left to be dealt with for the File System.

- Memory Mapped Files!!!
- Caching System
- Device Driver Specs
- Dynamically Linked Library accessing Device Driver or Server/Daemon
- File sharing, locking, etc... (need to be put on paper)

Currently available documentation:

- FSdoc0_3.txt Specs on current FileSystem.