MINIX file system
From Wikipedia, the free encyclopedia
| MINIX file system | |
|---|---|
| Developer | Open Source Community |
| Full name | MINIX file system |
| Introduced | (MINIX 3.1.2) |
| Partition identifier | |
| Structures | |
| Directory contents | |
| File allocation | |
| Bad blocks | |
| Limits | |
| Max file size | |
| Max number of files | |
| Max filename length | |
| Max volume size | |
| Allowed characters in filenames | |
| Features | |
| Dates recorded | |
| Date range | |
| Date resolution | 1s |
| Forks | |
| Attributes | |
| File system permissions | {{{file_system_permissions}}} |
| Transparent compression | No |
| Transparent encryption | No (provided at the block device level) |
| Supported operating systems | MINIX 3 and Linux |
The Minix file system is the native file system of the Minix operating system.
Contents |
[edit] History
Minix was written from scratch by Andrew S. Tanenbaum in the 1980s, as a Unix-like operating system whose source code could be used freely in education. The Minix file system was designed for use with Minix; it copies the basic structure of the Unix File System but avoids any complex features in the interest of keeping the source code clean, clear and simple, to meet the overall goal of Minix to be a useful teaching aid.[1]
When Linus Torvalds first started writing his Linux operating system kernel (1991), he was working on a machine running Minix, so the initial releases based a lot of functionality on Minix subsystems.[2] Until the April 1992 introduction of the Extended file system, Linux used the Minix file system.[3] The format is still used by some Linux distributions for bootable disks and other situations where a simple and compact file system is needed.
[edit] Design and implementation
A Minix file system has six components:[1]
- The Boot Block which is always stored in the first block. It contains the boot loader that loads and runs an operating system at system startup.
- The second block is the Superblock which stores data about the file system, that allows the operating system to locate and understand other file system structures. For example, the number of inodes and zones, the size of the two bitmaps and the starting block of the data area.
- The inode bitmap is a simple map of the inodes that tracks which ones are in use and which ones are free by representing them as either a one (in use) or a zero (free).
- The zone bitmap works in the same way as the inode bitmap, except it tracks the zones
- The inodes area. Each file or directory is represented as an inode, which records metadata including type (file, directory, block, char, pipe), ids for user & group, three timestamps that record the date & time of last access, last modification and last status change. An inode also contains a list of addresses that point to the zones in the data area where the file or directory data is actually stored.
- The data area is the largest component of the file system, using the majority of the space. It is where the actual file and directory data are stored.
[edit] References
- ^ a b Tanenbaum, Andrew S.; Woodhull, Albert S. (1997). Operating Systems: Design and Implementation, Second edition, Prentice Hall. ISBN 0-13-638677-6.
- ^ Torvalds, Linus; Diamond, David (2001). Just For Fun. Texere. ISBN 1-58799-080-6.
- ^ Card, Rémy; Ts'o, Theodore; & Tweedie, Stephen (1994). Design and Implementation of the Second Extended Filesystem. Proceedings of the First Dutch International Symposium on Linux. Retrieved on 2007-03-23.
