For most things, this is not a good way to approach system management. If you do this, RPM will not accurately describe your system, making management much more difficult than it needs to be.
I think you'll find that actually installing software on a new image takes far less time and people time than trying to come up with some magical scheme to be able to swap things in and out at will _and_ keep your RPM database corresponding to reality. In most cases, configuring/customizing the software is what takes the most time, and that won't go away no matter which route you take. Having a couple of basic system templates that then get customized for a particular use seems to be a good compromise. Levanta, for example, does this, and adheres to strict RPM dependency checking, which is the equivalent of not going "outside" of SMP/E or SES to get something working. A good idea, but sometimes difficult to stick to in the Linux world. As you install more and more Linux guests, you will eventually be able to justify the (unfortunately expensive) commercial management tools such as Levanta, Aduva, and BMC market. You don't want to invest too much time coming up with a scheme that is completely incompatible with where you're going to wind up when you acquire one of those tools. Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter Sent: Wednesday, March 22, 2006 3:11 PM To: [email protected] Subject: VM MDISK assignments for Linux files -snip- ...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. ---------------------------------------------------------------------- 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
