A VM shop looking at Linux for the first time would get a lot
out of comparing traditional CMS layout to traditional Unix layout:
190 -- boot and OS
191 -- private stuff
192 -- optional private or semi-private stuff
...
19D -- doc
19E -- "extra" OS stuff
19F -- local things
...
319
31A
Compare to:
/boot -- a real filesystem, but usable by the IPL text
/ -- private stuff (per Linux instance)
The problem with these two is that /bin and /lib
and /sbin are physically in the root FS (private).
There's no easy way around this.
/opt -- optional stuff (depends on your defn of "optional")
...
/usr/man -- doc (but there are others) and now /usr/share/man
/usr -- "extra" OS stuff
/usr/local -- local things
This does not account for /tmp and /var.
On any Unix or Linux, they can be part of the root FS
or they can be separate. Experience drives your choice.
But Unix (and Linux) has grown up a bit. A more complete list is:
xx0 (inspired by 190)
/boot
xx1 (inspired by 191)
/
xx5
/var
xx7
/tmp
xxE (inspired by 19E)
/usr
/usr/share
/usr/local -> ../local
xxD (inspired by 19D)
/usr/share/man, /usr/share/info, /usr/share/doc
xxF (inspired by 19F)
/local
xxA or xx9 (inspired by 319 and/or 31A)
/opt
xxB
/usr/src
But remember, this is driven by your experience and your needs
and most of the addressing is arbitrary. (Note that while CMS uses
standard addresses for known purposes, CP does not care and no shop
uses the same addresses as another for CP volumes.) I don't even
use this scheme, my own invention (inspired by CMS), except that
I did recently create a three partition 1BD disk for /usr/share/man
and /usr/share/info and /usr/share/doc, and I'm still pushing 1B0
as a common boot disk with 1B1 as a known standard root for it.
Mike ... I hope this helps.
-- R;
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
