Hi All,
I'm trying to upgrade a bunch of 4.0D workstations to 5.0A by
upgrading one, and then taking copies of / and /usr onto the others.
This has worked well in the past for systems below 5.n;
all I then had to do was modify a couple of files containing
ipaddress/names and off they went.
5.n seems to have changed all that. When I boot up a system
onto which I've installed a copy of / and /usr from my base machine,
I get problems with device recognition. The machines are, in principle,
identical (apart from memory sizes), and yet when I boot the machine onto
which I've installed the copy, the boot fails because it cant mount my
root filesystem, and drops into singl-user.
I then see things like:
hwmgr -sh scsi:
SCSI DEVICE DEVICE DRIVER NUM DEVICE FIRST
HWID: DEVICEID HOSTNAME TYPE SUBTYPE OWNER PATH FILE VALID PATH
-------------------------------------------------------------------------
-52: 0 cdrom none 2 1 null [0/0/0]
-54: 1 disk none 2 1 null [1/0/0]
I dont understand the negative numbers for HWID.
a 'hwmgr -scan scsi' doesnt change anything. The above output remains the
same.
Is there some way I can boot up into single-user mode from the 5.0 CDROM
and reproduce what the installation/upgrade process does when it scans
the hardware on a system and writes the initial hardware files to the
target root filesystem?
If I delete the whole hardware database stuff (whatever that may be)
and reboot the machine, will the files be automatically recreated?
As usual, any and all ideas welcome.
Cheers,
Terry.
Terry Horsnell (tsh_at_mrc-lmb.cam.ac.uk)
Computer Manager
Medical Research Council
Lab of Molecular Biology
Hills Road
CAMBRIDGE CB2 2QH
U.K.
Phone: +44 (0)1223 248011
Fax: +44 (0)1223 213556
Received on Mon Oct 30 2000 - 20:44:22 NZDT