Consider placing /var in its own space as well; this is all the log files, mail files, spool files and such, and will be very active. Leaving it in root has two drawbacks: It will cause your root to change, forcing its backup, and it could be overrun, causing your root to fill, which can be... Annoying.
Consider setting up LVM, the Logical Volume Manager, for several / most / all of these, so that additional space can be added with as little disruption as possible. Going the "all LVM" route requires that /boot be its own minidisk; everything else can be logical volumes, including swap. We set up a System VG, an Apps VG, and a Local VG. Local gets /home, System gets swap, /, /var, /tmp (as separate logical volumes). Apps gets /opt, /usr/local, and anything else specifically needed by the application(s) installed on the system after the distribution has been installed. -- Robert P. Nix Mayo Foundation RO-OC-1-13 200 First Street SW 507-284-0844 Rochester, MN 55905 ----- "In theory, theory and practice are the same, but in practice, theory and practice are different." -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter Sent: Wednesday, March 22, 2006 2:11 PM To: [email protected] Subject: VM MDISK assignments for Linux files We've just finished installing SLES9, WAS, MQ under z/VM and are preparing our actual Proof of Concept tests. In the meantime, assuming (but you already know it will) that this passes the P.O.C. objectives, I've been toying around with the VM minidisks locations that all this O.S. stuff, products, apps, and user data actually gets written to. To begin with, we'll be backing up the MDISKs with VM:Backup. That means that *any* change to anything on an MDISK will cause the full MDISK to get backed up. The amount of data can grow pretty quickly (right?), so I'd like to break things out onto separate MDISKS for to minimize backups of unchanged data, and very importantly, allow us to swap kernels, products, and business ass in and out by simply swapping MDISKs. We've come up with the following guidelines for Linux guests, but being the Linux newbie on the block, I'd appreciate suggestions. Might as well learn from others' hard-learned experience before we fight the same battles all over again! I hope this makes is through without lines being shifted to the left margin! MDISK range Usage ----- --------------------------------------------------------- 0191 CMS files... e.g. Filename Filetype LIN EXEC LIPL EXEC PROFILE EXEC SLES9 INITRD SLES9 KERNEL userid NETLOG LINUX PARM LINUX... 0200 SWAP (IBM recommends real DASD over VDISK) 0290 Kernel, /root (thinking of 290 as the CMS DISK for Linux) 0291 /tmp (thinking of 291 as the userid local disk, like the CMS 191) 0390 /apps (small MDISK, pointer to other File Systems) 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) 0490 /home (small MDISK, pointer to other File Systems) /lxuser1 (example, user files) /lxuser2 (example, user files) Thanks in advance. Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
