That's true, bind mounts are scary at first but not so bad after some use.
I would not use the technique unless I had quite a number of clones and as
you say, very strict policies. I am like the original poster and wondering
how cloing in the VM environment is being done (while also sharing as much
as possible). This was the only documentation I found on it. If you are
aware of how this can be done without the - - bind mounts, I would
appreciate any description on it (or a pointer to somewhere). I know there
must be other ways to integrate the cloning/sharing process with VM's
capabilities.
Adam Thornton
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
mine.net> cc:
Sent by: Linux on Subject: Re: Cloned guests and upgrades
390 Port
<[EMAIL PROTECTED]
IST.EDU>
07/03/2003 07:53
AM
Please respond to
Linux on 390 Port
On Thu, 2003-07-03 at 09:49, Richard Masuda wrote:
> There is a redbook at the z/vm site that may help you. It discusses the
> use of a basevol (containing shared r/o code) and mounting a guestvol
> (server unique code r/w over the r/o basevol directories). For example,
> the basevol is initially built and it has an /etc. The clone will link
r/o
> to the basevol /etc. In the startup scripts for the clone a minidisk
that
> is r/w is mounted over /etc using the mount - - bind option. It looks
good
> in the redbook and I have tried it with a couple of linux clones. It
seems
> to work, although I have had some problems with some process trying to
> write into a r/o directory. Anyhow, the book explains it much better.
Oh, yeah. Forgot bind mounts. They're a little scary at first, and a
lot of sites don't like to implement them because unless your Linux
admins are really sharp it's easy to forget what is r/o vs. r/w, but
they are a really cool way to save a lot of DASD. Again, you need
well-specified policies and procedures before applying service in this
sort of environment.
Adam
