Hi all.
I got one very helpful and motivating response from
Thomas Sjolshagen Thomas.Sjolshagen_at_hp.com (TS)
Also later an answer from Mike Broderick broderic_at_MIT.EDU (MD)
Thank you both.
I checked most of the issues by a new instal of V4.0G on a former V4.0D
system (I had only this Turbochannel box free therefore I could not
check it with V5.1B. Unfortunately I ran into new troubles, got a
mandatory system on the small box without AdvFS!)
I list here my original questions(Q) together with the answers(TS,MB).
Q: May I copy the subdirectories from old /etc/fdmns into the new one as
to include the old domains? Do I have also to copy the .advfslock_domain
files?
TS: No, device names changed from rzXXn to diskXXN
MD: The device names will all change in 5.x (e.g., /dev/rzXX to
/dev/disk/dskXX) so there's no need to save them :-). You may want to
save output from 'scu show edt' so you know the bus/target/lun (that
shouldn't chage) and can remap things after the install. (You can also
rename devices w/ "dsfmgr -m old new" if you don't like the order they
appeared in. You can also use "dsfmgr -O ..." to create the old v4
device names until you get all your scripts fixed.
Q:What is the most efficient way to get the file system information from
the other connected disks into the new system?
TS: Use /sbin/advfs/advscan
(My comment: But advscan gives no information about the filsets.
Answer TS: Try to mount with the old fileset names if known. Comment:
Are known because I have fstab)
Check: Worked fine. From a former listing (advscan - a) I could get back
all domains with
advscan -r rzX. Then renamed the new domain names to the old ones.
Copying back the saved fstab and a mount - a gave me the old disk
environment.
Printers:
Q: Is it sufficient if I copy (from backup) the old
/etc/printcap and the /etc/spool directory? (The /usr/adm/lperr files
will probably created when needed).
TS: Yes
Check: Worked in principle.
Q: Because no local printers are connected (only network ones, tcp or
lat) I probably don't need /dev/MAKEDEV lp?
TS: Correct
Mails:
QUESTION 4: If I copy the /var/spool directory I get also
/etc/spool/mail, is this sufficient that the users have there mails
afterwards?
TS: The sendmail changes in V5.1B require new mail configuration.
Afterwards copy /var/spool/mail to the directory sendmail uses.
Check: not checked
LAT setup:
I will do a latsetup just to get all /dev/lat/xxx devices.
QUESTION 5: If I copy back the old /etc/latstartup.conf and
/etc/securettys do I have everything? (The /etc/inittab will get the lat
getty information by latsetup anyway)
TS: No experience
Check: Creating LAT ttys with latsetup, copy old latstartup.conf,
securettys to /etc
gave the old environment.
NIS Setup:
Of course I want to continue with the old master/slave/client
configuration.
QUESTION 6: If I copy back the old /var/yp/<nis-domain> directory and
the /var/yp/src directory on the master server, is this sufficient? (I
could run a nissetup afterwards anyway to check it (using modify )?)
TS: --
Check: This is obviously not as simple as I inspected. After restoring
the old /var/yp files, the nissetup did not recognize it and wanted a
new setup. Then I edited the old NIS settings in /etc/rc.config. Again
calling nissetup showed me the node information and gave the option
"modify". But without completing nissetup NIS was not working. I had to
complete nissetup
Result: For a NIS client or slave it is better to run a fresh nissetup
The question is what happens when I re-instal the master server. I guess
I will restore /var/yp, then run nissetup with master and hope that it
afterwards uses my old files (passwd, group etc.)
Devices:
Old scripts may relate to the former device naming like /dev/rmt0h
instead of /disk/*tape/tape0_d0 etc. or for cdrom /dev/rzxx instead of
/dev/disk/cdrom0c.
Q: This has probably all to be changed manually?
TS: Yes
Last not least:
If I copy back the /etc files
fstab, exports,
hosts,hosts.eqiv,hosts.allow,bootptap,routes,resolv.conf,shells
(securettys as mentioned above)
I should have most of my old basic configuration. These are the only
files I remember to have made changes on in the past.
Q: Did I forget something important?
TS: Consider changes in /etc/sysconfigtab. But not copy, edit the old
changes into the new sysconfigtab (Comment: Good idea)
SUMMARY (my personal action/check list, at least till now):
- New Installation
- advscan -r rzX
- restore /etc/fstab
- mkdir old mount points
- mount -a
- netsetup, nfssetup
- nfs mount the disk with the backup files
- copy from old /etc/ to new /etc:
printcap
latstartup.conf
hosts.*
resolv.conf
routes
securettys
ftpusers
motd
bootptab
tftptab (one some systems)
shells
- restore /var/adm/lmf/ ldb and ldb_history (get license database)
- compare /etc/sysconfigtab, edit changes from old /etc/sysconfigtab
- copy -i /usr/skel/* to /usr/skel
- copy /var/spool/lpd* to /var/spool
- mkdir /var/yp
- restore /var/yp/* (only for NIS master)
- do latsetup
- do nissetup (using modify)
- Check:
/etc/inittab for lat gettys
/usr/sys/conf/NODENAME for changes made to the old system
- doconfig (if necessary)
This didn't work:
- restore my old additional shells (in particular bash)
(There was a library conflict even between V4.0G and V4.0D)
In the Digital/Compaq/Hp upgrade manuals one can often read "if your
system is old, better do a new installation". But if these advices are
meant seriously one should provide us (normal customers) with a
checklist, what to do in this case. Because I didn't find something in
this direction, that was the reason for this request to the list.
Regards
Otto
BTW, I am a more happy VMS than Unix system manager
-------------------------------------------
| Dr. Otto Titze, Kernphysik TUD |
| Schlossgartenstr. 9, D-64289 Darmstadt |
| titze_at_ikp.tu-darmstadt.de |
| Tel: +49(6151)16-2916,FAX:16-4321 |
-------------------------------------------
Received on Wed Mar 19 2003 - 14:48:40 NZST