January 2003
Intermediate to advanced
480 pages
13h 22m
English
Content preview from UNIX Filesystems: Evolution, Design, and ImplementationBecome an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Other Pseudo Filesystems
There are a large number of different pseudo filesystems available. The following sections highlight some of the filesystems available.
The UnixWare Processor Filesystem
With the advent of multiprocessor-based systems, the UnixWare team introduced a new filesystem type called the Processor Filesystem [NADK92]. Typically mounted on the /system/processor directory, the filesystem shows one file per processor in the system. Each file contains information such as whether the processor is online, the type and speed of the processor, its cache size, and a list of device drivers that are bound to the processor (will run on that processor only).
The filesystem provided very basic information but detailed enough to get a quick understanding of the machine configuration and whether all CPUs were running as expected. A write-only control file also allowed the administrator to set CPUs online or offline.
The Translucent Filesystem
The Translucent Filesystem (TFS) [HEND90] was developed to meet the needs of software development within Sun Microsystems but was also shipped as part of the base Solaris operating system.
The goal was to facilitate sharing of a set of files without duplication but to allow individuals to modify files where necessary. Thus, the TFS filesystem is mounted on top of another filesystem which has been mounted read only.
It is possible to modify files in the top layer only. To achieve this, a copy on write mechanism is employed such that files ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.