I recommend that you force the issue.
As Marcy said, many packages will not give you the option
of where to put them, but with time you can understand where
they are putting themselves.
Read-only disks need to be backed up less often.
It does not appear that you have split out /usr and /opt
into their own disks. You should. You should then also
make those read-only so that you will know when something
gets placed there (by the dreaded RPM, for example).
0191 -- CMS, back it up because VM:Backup groks it
0200 -- swap, no need for "backup" per se, but may want quick re-create
0290 -- kernel and root
Split this into at least two disks
put /boot into its own disk and make that RO.
0291 -- /tmp, some people remove old content from here so you
may consider not backing it up (except for quick re-create)
0390 -- /apps ... is this a directory of sym-links?
Might could make this a directory in the root FS.
x39x ...
/local (call it what you will, locally-written business apps)
/wasmq (example - vendor app)
x39x /db2 (example - vendor app)
x39x /domino (example - vendor app)
-- Each of these should be its own disk.
Consider moving the supplied /usr/local to /local
(and then /usr/local being a sym-link to the new location).
But /wasmq, /db2, and /domino should each be its own FS
(be on a separate disk). I fear, though, that they will
be read-write. You MAY be able to get /local to be RO.
0490 ...
/home (small MDISK, pointer to other File Systems)
/lxuser1 (example, user files)
/lxuser2 (example, user files)
-- Mike, I'm not following.
Are you suggesting to partition your 490 into three FS?
Fine. Doesn't buy you much, but if it helps your team
get a mental handle on this, it's a win. But these
all three would/should be RW and backed up most often.
-- 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
