My original message:
>
> We have a Dec3000-M600. We just got an AlphaServer 1000A 4/266 and
> we would like it to replace the 3000-M600. Has anyone done this
> before? Have any advice? How much of the old machine can I just
> copy over and use?
>
> We would like this to be transparent to users, of course. I'd like
> the new machine to look as much like the old machine as possible.
>
> Oh, and the machines are running Digital Unix.
>
Most folks thought we could do it either by booting off the 3000's genvmunix
or by copying over config files. I did the latter. It's a long process,
though. Between homegrown software and installed software, there are lots
of little differences that I need to fix. And customized files are hiding
in the darnedest places.
Here's what some folks said:
Ken Teh <teh_at_chinook.phy.anl.gov>
If your old machine is running the latest kernels, then you should be able
to "copy" over the old machine onto the new machine. If the kernel does
not support the new hardware, then you will have to upgrade your OS. But
a Unix machine is pretty much like any other Unix machine, and in particular,
a DU machine should be like any other DU machine.
ohad_at_comport.com
Do a fresh install on the 1000, and then copy all the needed config files in
/etc /sbin/init.d .....
alan_at_nabeth.cxo.dec.com
If the version of Digital UNIX supports both systems
there are a very small number of changes that have to
made to reuse the current system disk. My experience
as been:
1. Boot the generic kernel and build a system specific
kernel.
2. Edit /etc/rc.local to use the different network device
name.
3. If the system disk moves to a different device name,
have the special device files created for it ahead
of time.
4. If the system supports graphics and you're on a version
of Digital UNIX that uses multiple X server subsets,
be sure to have both sets of X servers installed.
David Bremner <bremner_at_cs.mcgill.ca>
Well, I replaced a 3000/500 with a 1000/233
essentially I just renamed the two machines, and that was that.
I can't remember the exact steps in changing the names
of the machines, but if you search the mailing list archives at
http://www.ornl.gov/cts/archives/mailing-lists/search.html
you should find it
Huw Davies <H.Davies_at_latrobe.edu.au>
I haven't done this particular migration but have done others so I've added
a few
of the things that you need to check before doing the change (and some of
the things
that I've been burnt with :-)
1) Ensure that you're running a version of DU that is supported on the
destination
hardware - if necessary upgrade the old system first.
2) You MUST (I mean MUST) have a copy of genvmunix on your system disk. It's
really
bad to move the disks across to the new system and then not be able to boot
it....
3) After booting from /genvmunix, rebuild the kernel from scratch. This
means removing the configuration file and (in one upgrade that I did)
removing the associated binaries. Assuming your system is called FRED,
remove the file /sys/conf/FRED and the files /sys/FRED/*.o The run
/usr/sbin/doconfig to build a new configuration - I guess if you've got
special kernel parameters, you should save a copy of /sys/conf/FRED to refer
to (on one upgrade I forgot to increase the maximum number of users - our
web server wasn't too happy...).
>We would like this to be transparent to users, of course. I'd like
>the new machine to look as much like the old machine as possible.
Given the above restraints, the move can be transparent (apart from the
performance increase).
Received on Wed Nov 06 1996 - 18:04:47 NZDT