Nix, Robert P. wrote:
I'd say that your best bet (and speediest method to get up and running) would
be to just install Linux again on the second LPAR, and do the same
customizations you did on the first one. Cloning takes some additional planning
and setup before you'd be able to successfully pull it off, especially without
the aid of zVM virtualizing the hardware addresses.
At some point in the build, after the actual system is installed and running,
you might be able to just scp the application directories over to the second
box to the first one via TCP/IP.
I've recently discovered that, while it's extremely convenient, that
it's also slow on fast networks.
The problem is that encrypting the datastream costs.
I'm now using NFS over mmy popular LAN routes.
If you want to clone a system using just Linux, booting one on some kind
of starter system and mounting the other via NFS, or using NBD or
similar (I've not tried it) should work well.
For small numbers of systens I think I'd use kickstart. Anaconda
produces a ks file whenever you install, and this will allow you to
install customised replicas from the one kickstart.
Replicas because they've gone through the same install process, not
clones which have gone through a different process from the original.
An advantage of kickstart over cloning is that Anaconda automatically
takes account of any hardware differences, and sets up IP addresses and
host names automatically.
You can also do your customisations in your own scripts as part of the
install process.
SUSE also has automated installs, but of course the tools are different.
--
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
