Summary of my Digital UNIX v4.0 installation.
Received the Digital UNIX v4.0 installation/update kit.
Found missing the Firmware CD - no problem, it's all on ftp.digital.com.
NOTE: Claes Sandgren <csa_at_soo.dec.com> sent me a message stating that:
|>Just a thought:
|>v3.5 sould suffice, v3.6 is for V3.2F
|>(
ftp://ftp.digital.com/pub/Digital/Alpha/firmware/v3.5/doc/)
|>/Cheers
I went ahead with v3.6 per the Release Notes Addendum (page 7: "Firmware
for DEC 3000 Series Processors"). Perhaps 3.5 would suffice?
Here's what I did and what happened to me - YMMV.
First thing I did was to do a single user level 0 dump of /, /usr, and /var.
Next I restored my system to what Digital UNIX expected (adding and removing
symbolic links to make it consistant with what DU expects).
Then I deleted appropriate subsets as mentioned in Section 2-5 (page 2-7 of
Installation Guide.
**Here's your chance to make a big difference in the installupdate time -
also delete any subset you are not using. I didn't and had 80 subsets to
load during the installupdate**
You may also wish to delete any subset you've got loaded which is listed in
the "Read This First" document pages 4 and 5 (you'll have earlier versions
than those listed, but you'll save other problems, more on this later)
Next, the firmware update...
Since I pulled the binaries from Digital's FTP site, hence no CD,
I had to do a remote installation/boot for the files.
Problem, my workstation was the only RIS server configured, and I was going to
upgrade it.
I didn't feel like installing another RIS server (yet), so I dumped the two
files as appropriate for my DEC 3000 onto a VAX/VMS system (into mom$load)
then 'MCR NCP set circuit isa-0 state off'
'MCR NCP set circuit isa-0 serv enabled'
and 'MCR NCP set circuit isa-0 state on' on the VAX.
then back to my workstation: >>> b esa0 -fi "M300_V6_7.SYS", and voila
firmware update menu.
Then I booted "TC_V2_0.SYS" (turbochannel firmware) the same way.
back to console mode - power off for a short spell, and power on to finish
firmware update.
boot to single user mode.
/sbin/bcheckrc
df # see how much available space you've got (see appendix F (pages
F-14 and F-15) for amount required.) Then make sure you've got about 1 MB
additional in each of the partitions.
I ran installupdate -i /dev/rz#c multiple times due to failures in amount of
disk space free.
next to last time, it wanted a total of 24866 512-blocks free (appendix F for
DU-3.2D-1 is a couple of Meg lower, but in all fairness, Digital states that
additional space is required for "processing and temporary files". I just
didn't expect that much.
Then the 80 subsets to install portion started.
2.25 hours later, subsets finished loading from my RRD42-VA to my RZ28-VA (175
Mhz 3000 with 160Mb RAM).
**Note, support for up to 115.2K baud modem rates scrolled across the screen!**
Just immediately prior to rebooting on DU 4.0, I saw a mv syntax error -
appears to have been benign. Installupdate told me it was successful doing
the update installation, hence, at this time it appears benign.
System rebooted then configured and merged all the subsets.
Kernel was rebuilt, but since I had the SCSI CAM utilities (v3.0) on my
system, the rebuild failed the first time, but when the system tried again,
it succeeded.
I logged in as root, deleted the SCSI CAM utilities (and more, like NSR), ran
a doconfig with no options or parameters and selected the options desired.
then ran /usr/sbin/updadmin for the post installation cleanup tasks.
next I loaded all the new subsets appropriate for my workstation
and then ran catman -w to rebuild the whatis database.
Now I'm quickly getting used to CDE.
Other comments:
I really like the robustness of the new installupdate - if I had sufficient
free space on / to start with, after answering yes to continue about 2
minutes into the upgrade, I could have walked away, came back hours later and
the installation would have completed.
I like the new format of the distribution CD.
CDE takes some getting used to, but I'm getting familiar with it - it just
took me about 10 minutes to find a terminal icon to open at first.
Bottom line:
I have had no major problems (only a couple of minor ones) installing DU 4.0,
and am now starting testing of applications...
Randy M. Hayman
haymanr_at_icefog.alaska.edu
Received on Fri Jun 14 1996 - 16:22:46 NZST