I wrote my summary on this topic a little early because i just received a
VERY usefull tip from Tom P. Blinn that i quote below:
<<<<
One of the recommended steps was to compare your changes in the key
system files to the originals and then just merge your changes into
the files after the new install. That is a good idea.
For a LONG time, Tru64 UNIX has had the concept of protected system
files, that is, files that are delivered in the kit but that should
NOT simply replace an existing file because the user is expected to
modify the file -- things like /etc/rc.config and /etc/sysconfigtab
and the various /etc/*.conf files are examples, there are others.
Each such file is delivered in the current kits with a ".new.."
prefix on the name (so it won't overlay the "real" file), and there
is a step where the .new.. files are either simply copied to make
the .proto.. files of the name base name, and then the "real" file,
or in an update, the .new.. file is compared to the .proto.. file
from the prior version and the differences are merged into the "real"
file, then the .new.. is copied to define the latest .proto.. (it's
actually merged in). It's a messy process, but it works, and it's
very useful, because the old .new.. and .proto.. files from your old
system are very useful for finding what you changed
>>>>
______________________________________________
Maurice Steyvers, ICTS, Universiteit Maastricht
mailto:maurice.steyvers_at_icts.unimaas.nl
phone :(++ 31 43) 388 23 49
Fax :(++ 31 43) 361 42 87
_______________________________________________
> -----Original Message-----
> From: Maurice.Steyvers_at_ICTS.UNIMAAS.NL
> [mailto:Maurice.Steyvers_at_ICTS.UNIMAAS.NL]
> Sent: 28/03/01 8:53
> To: tru64-unix-managers_at_ornl.gov
> Subject: SUMMARY: Upgrade from 4.0f to 5.1 or full install ??
>
>
> As expected opinions differ on this subject (about 50% in
> favour of upgrade
> and the other 50% choose full install).
>
> I think i'll go for the full install, some interesting
> remarks i received
> from g.j.hilbrands_at_kpn.com on this are:
> <<<
> - v5.1 has a new Advfs file structure which is not downwards
> compatible with
> the 4.0X Advfs structure. You can mount v4.x advfs file
> systems on a v5.1
> system but not the other way around. When you create a new
> filedomain/fileset combination on a v5.1 system it will
> automatically take
> the newer advfs structure. When you definitely want the old
> advfs structure
> you can use a parameter with your mkfdmn command.
> - The files you mentioned in your mail are the most important
> to restore. It
> is not wise however to just restore the files. I would use
> the original
> (fresh) installed files on your new system and add the
> changed entries from
> the files on the 4.x system. Be careful with the
> /etc/sysconfigtab, because
> there have been some changes in some parameters. Be sure to check the
> existence of the parameters with sysconfig, before implementing them.
> >>>
>
> An other interesting reaction from Pat O'Brien on the upgrade
> traject is:
> <<<
> I too have been analyzing the same move from 4.0f to 5.1. I
> have selected
> 4.0f pk4 (my current version) to 5.0a to 5.1 and then pk2. I
> have been
> testing on alphaservers 1200, and have uncovered several
> traps(read 5.1
> relaease notes on lsm (voledit set lsmvol =bsd4.2)). I then
> did my first
> production system which did preety much as you described and then some
> trashing my system. recovered the system, and redid, and presto same
> results. Opened call to dec support, and there are bugs in
> the 5.0a which
> do this on 2100, es40, & 500au systems. They recommend goin
> to 5.0 then
> 5.1, as this bug seems according to them a 5.1 issue. I dunno as we
> re-evaluate.4.0g really is nothing more than hardware release
> for wildfire.
> >>>
>
>
> As usual thanks to you all,
>
> Maurice
>
> > -----Original Message-----
> > From: Maurice.Steyvers_at_ICTS.UNIMAAS.NL
> > [mailto:Maurice.Steyvers_at_ICTS.UNIMAAS.NL]
> > Sent: 27/03/01 15:29
> > To: tru64-unix-managers_at_ornl.gov
> > Subject: Upgrade from 4.0f to 5.1 or full install ??
> >
> >
> > For our three SAP R/3 servers (4.6B with Oracle 8.0.6.1)
> > we're planning a
> > hardware replacement (eg Alpha 1000A replaced by ES20). At
> the current
> > systems we are using Tru64 UNIX 4.0E en 4.0F but
> unfortunately the new
> > hardware requires Tru64 UNIX 5.1 (to be able to boot from
> storageworks
> > device or something).
> >
> > I see two possible ways to get to from 4.0F to 5.1.
> >
> > 1: upgrade the old system from 4.0F -> 4.0G -> 5.1 + SP2,
> > backup system on
> > old hardware and restore whole system on new hardware, build
> > new kernel and
> > run...
> > 2: install new Tru64 UNIX 5.1 + SP2 on new hardware, create
> > same filesystems
> > on new system like on old system, backup the old system ,
> > restore only the
> > SAP en Oracle file systems on the new hardware, restore
> > important UNIX files
> > like /etc/passwd, /etc/fstab and so on on the new hardware,
> > adapt some UNIX
> > kernel parameters as required by SAP/Oracle and run...
> >
> > >From scenario 1 you might expect the least problems at the
> > cost of relative
> > long run-time whereas scenario 2 is much quicker but also trickier.
> > I've tested scenario 1 (which was my first choice) on a Alpha
> > 2100 and ran
> > into some strange problems (/usr/bin/getopt had size 0 bytes
> > after upgrade,
> > wrong protection of /etc/sia/matrix.conf after upgrade,
> problems with
> > enhanced security database) so at the moment i'm thinking of
> > trying scenario
> > 2.
> >
> > Which scenario do you advise ?
> >
> > I've made up a list of relevant UNIX files that need to be
> > restored, do I
> > miss something important ?
> > /etc/passwd
> > /etc/group
> > /etc/fstab
> > /etc/hosts
> > /etc/services
> > /etc/inittab
> > /etc/rc.config
> > /etc/exports
> > /etc/resolv.conf
> > /etc/sap.conf
> > /etc/listener.ora
> > /usr/local directory + subdirs
> > crontab and shutdown scripts
> > $HOME/<sid>adm
> >
> > Can i just restore these file (eg a file like /etc/rc.config
> > from 4.0f to
> > 5.1, i guess not) or do i have to carefully look what changed
> > and adapt the
> > file as needed.
> >
> > Do i overlook anything in scenario 2 ???
> >
> > Maurice
> >
> >
> >
> > ______________________________________________
> >
> > Maurice Steyvers, ICTS, Universiteit Maastricht
> >
> > mailto:maurice.steyvers_at_icts.unimaas.nl
> > phone :(++ 31 43) 388 23 49
> > Fax :(++ 31 43) 361 42 87
> > _______________________________________________
> >
>
Received on Wed Mar 28 2001 - 11:54:33 NZST