Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
While we are on the subject of file systems and hstory. In more recent years the /var directory is commonly a separate file system because it contains highly volatile data (spool, logs, tmp) where /usr normally contains stable data. Additionally, on Linux, the /boot directory is notmally a separate file systems on large disks because of the 1024 cylinder problem. (Some systems use /stand for a similar purpose). /opt is another file system which normally contains optional subsets, such as compilers, 3rd party software. Clustering makes things very complicated where multiple computers (eg. nodes) share a common disk cluster. Each of these computers could be running a different version of the OS (eg. tru64 5.0, tru64 5.0a, etc). Since all the disks are shared (eg. non-local) it presents interesting problems since some files and some directories must be node-specific. An example would be /var/adm and /var/log. Got to go to lunch. On 28 Apr 2000, at 11:11, Mike Bilow wrote: <some snips> > The principle is that /var should be local. Before /var existed, we had > /usr/tmp, /usr/spool, and so on. Jerry Feldman <gaf at blu.org> Associate Director Boston Linux and Unix user group http://www.blu.org - Subcription/unsubscription/info requests: send e-mail with "subscribe", "unsubscribe", or "info" on the first line of the message body to discuss-request at blu.org (Subject line is ignored).
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |