.chroot?= MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 > The thought comes to mind that IF I were to follow my > OS/390 maintenance procedures, I might consider > cloning this system, then from my production system issue a mount of cloned > root to /SERVICE and chroot to /SERVICE to apply these RPM's.
This makes sense in the USS environment, where your current running system drives the installation of the cloned system volumes[1]. In a Linux/Unix setup, however, it's usually too easy to copy the disks to another machine and do the install over there. One way we can do this in a Penguin Colony: we can copy the DASD to new minidisks, bring up a new 'upgrader' drone penguin on those minidisks and do the upgrade. Then, update the directory for the upgradee penguins to use the upgraded minidisks. Now, you can upgrade a swag of penguins simply with shutdown-logoff-logon-IPL (once for each penguin). Others have mentioned that it's just as effective to simply switch to single-user mode and upgrade. This is great, as long as you only have a small number of penguins... Cheers, Vic Cross [1] For those who don't do OS/390, maintenance of the Unix System Service (USS) component of z/OS and OS/390 goes a bit like this: you make copies (clones) of your system filesystems, mount these copies under a special mountpoint (/service, according to current IBM convention), and tell the software maintenance system (SMP/E) to update files under that mountpoint instead of root (eg. /service/usr/bin instead of /usr/bin). Then you IPL the system off your new system volume, the configuration of which will mount the new filesystems. -- Vic Cross MACS mailto:[EMAIL PROTECTED] Networking, Linux, on zSeries and S/390
