So if I am reading your email correctly, for the duration of an major
update I would first "basically" update my master (as it is rw for
everything). Then each guest allocate a /usr filesystem that is throw
away. Mount that /usr as rw during the cloned guests updates. After the
updates I can simply unmount the rw throw away copy of /usr and mount the
masters /usr as ro, which has already been updated? Is this correct?
This could work, though would take a little caution and planning to avoid
a major screw up. In addition major updates may take a little longer to
push through a large environment.
Thanks!
Eric Sammons
Arnd Bergmann <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
01/27/2004 07:54 AM
Please respond to Linux on 390 Port
To: [EMAIL PROTECTED]
cc:
Subject: Re: Pros and Cons to sharing /usr
On Saturday 24 January 2004 22:54, Eric Sammons wrote:
> That still does not seem to address the configuration / binary mismatch
> that may occur between /usr and /etc. Each guest clearly has to have
its
> own /etc and /var so it is entirely possible to have a binary mismatch
> with the configuration files that reside in /etc. In addition, having
> thought about this further, the package database resides in /var. This
> also is unique to each system.
Well, you should probably read again. My proposal addresses exactly this
issue, nothing else. Note that the package database and other files
are being updated whenever you install the updates on all of your
guests. The trick is to make sure that after the upgrade, all the guests
still have the same data on /usr (because you install identical packages),
so you can use a shared /usr after you have done updates on your private
copy.
Arnd <><
