Tru64 new instal - but with old settings

From: Dr. Otto Titze (titze@ikp.tu-darmstadt.de)
Date: Mon Mar 17 2003 - 08:07:32 EST


Hi all,

I am not so familiar with Unix, therefore I have a few simple questions
concerning system management. I want to upgrade most of my systems
(except the turbo-channel ones) to Tru64 V 5.1B. I already tested that
all our prior applications run under this new version. Now I am looking
for a fast and efficient way to change the different systems, most of
them are V4.0D , even a few still lower..

I do not plan to upgrade ,because that means
V4.0B > V4.0D > V4.0G > V5.1 > V5.1B
and as it turned out that the partitions of the system disk has to be
changed a few times, therefore a direct new installation seems to be
more reasonable. The most applications I will re-instal anyway. I am
looking for the best way to get the former basic environment. I am
asking this because changes apply to a production environment and there
is not much time for me playing around.

The most uncertainty for me is to get back the old file system
information (all Advfs) of the other disks without to setup every
domain, fileset manually(mkfdmn, mkfset with the known old parameters).
I cannot copy /etc/fdmns to the system partition because there is a new
one there. It seems to be some tools there (advfsscan?) but I am not
familiar with that.

QUESTION 1: 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? What is the most efficient way to get the file
system information from the other connected disks into the new system?

The following questions are of minor importance:

Printer setup: I don't want to make a complete lprsetup at every system.

QUESTION 2: 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).
QUESTION 3: Because no local printers are connected (only network ones,
tcp or lat) I probably don't need /dev/MAKEDEV lp?

Mails:
QUESTION 4: If I copy the /etc/spool directory I get also
/etc/spool/mail, is this sufficient that the users have there mails
afterwards?

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)

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 )?)

Devices:
Old scripts 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.
QUESTION 7: This has probably all to be changed manually?

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.
QUESTION 8: Did I forget something important?

SUMMARY, what I believe has to be done
- New Installation
- netsetup
- nfs mount the disk with the backup files
- copy -i /etc/fdmns/* to /etc/fdmns (subdirectories only)
- copy all mount-points to system root /
- copy from old /etc/ to new /etc:
    fstab
    printcap
    latstartup.conf
    hosts.*
    resolv.conf
    routes
    securettys
    ftpusers
    license.dat (hopefully lmf will see my registered licenses)
    motd
    bootptab
    tftptab (one some systems)
    shells
- copy my additional shells to /usr/bin
- copy -i /usr/skel/* to /usr/skel
- copy /var/spool/* to /var/spool
- copy /var/yp/domain to /var/yp
- copy /var/yp/ src to /var/yp (at NIS Master)
- do latsetup
- do nissetup (using modify)
(this should make the proper entries in /etc/rc.config)
- Check:
    /etc/inittab for lat gettys
    /usr/sys/conf/NODENAME for changes made to the old system
- reboot
I hope this will work…

I would appreciate every hint. Thank you. I think is important for
people like me without a deep insight into the system to know the
consequences before. Because the complexity and tedious upgrade
procedures often results in the fact, that one stays too long with
outdated systems.

Of course I will provide a summary or script which contains everything.

Regards
Otto

 -------------------------------------------
| Dr. Otto Titze, Kernphysik TUD |
| Schlossgartenstr. 9, D-64289 Darmstadt |
| titze@ikp.tu-darmstadt.de |
| Tel: +49(6151)16-2916,FAX:16-4321 |
 -------------------------------------------



This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:11 EDT