On Thu, 2004-07-08 at 11:03, Levy, Alan wrote: > We tried making /usr a ro minidisk. It did not work for us. When we had > to upgrade our kernel using an RPM, it failed since it tried to load > files to the /usr which was not owned by the clone. > > How did you get around this ?
For applying maintenance, you need two additional disks: one contains a DDR image of the /usr disk before maintenance, and one is a scratch disk that gets a DDR image of the pre-maintenance-/usr, and is mounted r/w to the guest. You IPL the guest with that read-write volume in place, apply maintenance, shut down the guest, and reIPL with the shared (updated) read-only DASD. Then you reimage the scratch disk from the pre-maintenance /usr and move to the next guest. Yes, this is a big pain in the butt. If there's a better way to do this, please tell me. Doing it with filesystems in EW saved segments (which you then discarded in favor of a non-writable segment) might work but seems like it would consume a lot of real storage. Adam ---------------------------------------------------------------------- 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
