The ChorusOS operating system supports the following types of file system:
Network file system, NFS (client and server)
MS-DOS file system
UNIX file system, UFS
FIFOFS feature provides support for named pipes. It requires either
UFS to be configured as well as
For more details, seeFIFOFS(5FEA).
NFS_CLIENT feature provides POSIX-compatible file I/O system calls on top of the NFS file system. It provides only the client side implementation of the protocol and thus requires a host system to provide the server side implementation of the NFS protocol. The
NFS_CLIENT feature can be configured to run on top of either Ethernet, PPP or SLIP. The
NFS_CLIENT requires the
POSIX_SOCKETS feature to be configured.
For more details, see NFS_CLIENT(5FEA).
NFS_SERVER feature provides the services to provide an NFS server on top of a local UFS file system. It provides only the server side implementation of the protocol, the client side being provided by the
NFS_CLIENT feature. The
For more details, see NFS_SERVER(5FEA).
MSDOSFS feature provides POSIX-compatible file I/O system calls on top of the
MSDOSFS file system on a local disk. It requires a local disk to be configured and accessible on the target system.
At least one of
SCSI_DISK must be configured. It is usually embedded in any configuration which uses a file system as part of the boot image of the system.
MSDOSFS is frequently used with Flash memory.
For more details, see MSDOSFS(5FEA).
The UNIX file system option provides support for a disk-based file system, that is, the file system resides on physical media such as hard disks.
The UNIX file system option supports drivers for the following types of physical media:
For more details, see UFS(5FEA).