Dominic Coulombe wrote:
For an example, you can share RO the /usr filesystem. When you apply a patch on the main system which owns the disk in RW, your other machines ARE NOT aware of the changes until you re-mount the filesystem on each Linux machine.
I will put that a little more strongly: as soon as you update the master copy, _all_ the guests have entirely the wrong idea of where files are and what's in them: it's perfectly possible for space a client believes is used by one file to be replaced with data from another. I'd be planning on shutting down all the ro clients while the updates are done. I _think_ I'd have two masters, one to practice on and get right before going live, and at least one test guest in which to test it's right. Do you have a separate QA function to vet this? -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/ do not reply off-list ---------------------------------------------------------------------- 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
