I am in the process of upgrading a workstation from v4.0E PK#4 to v4.0F.
Everything went fine until the end. I got:
86 of 86 subset(s) installed successfully.
*** Merging new file ./etc/.new..inittab into
existing ./etc/.proto..inittab
Merge completed successfully.
*** Merging new file ./usr/var/spool/cron/crontabs/.new..root
into
existing ./usr/var/spool/cron/crontabs/.proto..root
cron may not be running - call your system administrator
Merge completed successfully.
*** Merging new file
./usr/var/kernel_options/.new..kernel_options.db into
existing
./usr/var/kernel_options/.proto..kernel_options.db
adding ATM UNI 3.0/3.1 ILMI option
adding Digital Versatile Disk File System (DVDFS)
Merge completed successfully.
/updmnt/isl/upeng: /var/adm/patch/event.log: cannot create
and I then get the system prompt: #
Upon inspection, it seems that the problem is that /var/adm/patch is a
symbolic link to an nfs file system (to save space). Perhaps this
may have been a dumb thing to do, but not half as dumb as the update
installation procedure that lets you do this without first checking!
Anyway, what should I do now? It seems that I have the new /genvmunix.
Can I boot /genvmunix and then run doconfig? How? Should I first
try to move /var/adm/patch physically onto to disk? Is the entire
directory necessary (i.e. including the doc and backup directories) or
is the log directory and product_map enough (should be)?
It seems to be that the installupdate procedure did not finish
configuring all the installed subsets, whatever that means.
Or do I have to choose between either a restore from backup of the
previous system (v4.0E pk#4) plus a new update installation or a clean
(full) install?
Thanks,
Peter Stern
Received on Thu Dec 07 2000 - 09:35:19 NZDT