From: Robert Fridman (fridman@ucalgary.ca)
Date: Tue May 07 2002 - 18:13:45 EDT
The consensus is that it should work once the 5.x device names are
sorted out. Some useful notes:
> Don't configure LSM at install unless you have to, it's easier to
> encap and
> mirror after the disk names get fixed. - "Davis, Alan"
> <Davis@tessco.com>
> You need to delete the temporary build files: rm -r
> /usr/sys/mysystemname
>
> You also need to run sizer -n myname and look in /tmp. There will be a
> hardware configuration id with the name cpu. You need to update your
> system's kernel configuration file with the id from the /tmp/myname
> file. - Jeffrey_Hummel@albemarle.com
> Yes and no. There is a boot flag you can use that causes the install
> to halt BEFORE it tries to reboot and configure the installed bits.
> If you use this, then you MIGHT get it to work (that's basically how
> the factory installed software image gets loaded). However, it may
> not work with a V5.x install because of all the stuff that's involved
> with the hardware persistency -- some things may get placed onto your
> new disk during the install that will make it just not work.
>
> In general, you can't move a fully installed/configured system disk
> to a different system model any more. There are procedures that a
> few people have developed (search the list archives) that appear to
> know what to remove to get it to work, but it's ugly. - "Dr.
> Thomas.Blinn@Compaq.com" <tpb@doctor.zk3.dec.com>
> If you try, after you move it to the DS20, be sure to boot off of
> CD, mount the drive and delete the hardware database.
> Greg Freemyer <freemyer@NorcrossGroup.com>
> The final gotcha is to remember to alter system config info
> appropriately prior to rebuilding the kernel to reflect the hardware
> you
> actually have in terms of network cards etc.
> "Ralf Borowski" <rborowski@tembec.ca>
> Sure, do it all the time.
>
> The "easier" thing to do is to just put them both on a SAN and then
> boot
> off the SAN disk image. (Note I said easier, not cheaper.)
>
> No tricks other than what you mention...
>
> However, building a new kernel is almost not even necessary anymore. I
> haven't tried it explicitly, but with 5.1A, "I think" all of the
> hardware
> configuration is all done at boot, so that building a new kernel is no
> longer necessary. The kernel options no longer include the hardware
> configuration! It's all part of the single-disk-image cluster
> environment
> (booting multiple systems from one disk image.) It allows all CPUs in a
> cluster to boot from one disk-image on the Cluster-File-System (aka
> SAN). I
> know that cabability is "in the pipeline," I haven't really read-up
> on 5.1A
> to know if it is all in place and operational. - "William H.
> Magill" <magill@isc.upenn.edu>
Thanks to all who replied
Origional question was
> Does anyone know if it is possible to install 5.1a on a disk in an
> ES40, then move the disk to a DS20, boot generic, build a kernel and
> have 5.1a running on the DS20?
Robert.
-------------------------------------------------------
Robert Fridman fridman@ucalgary.ca
MACI Cluster Computing Systems Administrator
Netera Alliance
University of Calgary
Phone: (403) 220-6779 Fax: (403) 282-9199
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:40 EDT