We use a variation of the Using BIND Mounts to Create A Simplified BaseVol/GuestVol Linux Server process outlined at: http://linuxvm.org/present/misc/basevol.html Instead of the REXX scripts, we used standard scripting. We have the / (root) and /opt file systems as R/O z/VM mini disks. The rest of the data is mounted in R/W LVMs. We maintain Linux in a 3-tier approach. A Maintenance Linux in which all updates and installs take place to the R/W / and /opt directories. These directories are then cloned to a Testing Linux where the / and /opt directories are only R/O. This is necessary to insure that no writes are attempted to the R/O directories. After we are happy with testing, we move the / and /opt directories to the ?Golden Linux? from which all Penguins share in a R/O mode. Some advantages are: We maintain one Linux but many virtual Linux guests. We can install products once and make them available to all Linux guests. If a Linux guest does not need them, they just do not use them. The cost is a R/O /opt which is necessary if only one Linux required a product anyway. Prevents accidental and/or unauthorized changes to Linux or its program products. Simplifies security, backup and recovery.
Some disadvantages are: We do not run many Linux guests yet and might have no idea what we are getting into. Must have a set of guidelines and procedures that must be adhered to. But then, making people play by the rules is not necessarily a bad thing. Some software might require repackaging or modification to insure R/O data goes to R/O file systems and R/W data goes to R/W file systems. I hope this helps ---------------------------------------------------------------------- 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
