---
Richard Rogers <R.M.Rogers_at_staffs.ac.uk>
/snip,snip/
I would always load the latest available firmware prior to upgrading the
OS. The last firmware CD I've seen is labelled v5.0, but the firmware
revision number depends on the hardware type. And I would do the firmware
first - I'm told that the firmware can't be too recent for the OS, but the
reverse is not true.
> 2) palcode version ?? (currently 1.35)
As for firmware.
> 3) how good is the automated upgrade?
It worked for me - in my experience the upgrade installations are pretty
reliable.
> 4) Would it be easier to store /etc/* /var/yp/* and start
> from scratch? eg CDROM installation
Depends how much customisation you've done - if only a little, then it may
be easier (or at least quicker) to reinstall from scratch and
re-customise; if on the other hand your customisations are reasonably
extensive (or not well documented), it may be easier to follow the upgrade
installation route.
> 5) Is there any documentation (according to Mark, apparently not)
Installation Guides, Release Notes...normally supplied with OS CDs.
One further note; when I did my upgrade, I went 3.2D -> 4.0 -> 4.0B ->
4.0D, but apropos another query to this list, I was told that 3.2D -> 3.2G
-> 4.0A -> 4.0D (I think that's how it went) might possibly be more
reliable (no more detail, I'm afraid).
---
Martin Mokrejs <mmokrejs_at_mail.natur.cuni.cz>
This was posted to the list, say half a year ago, maybe less. However, I'd
wait still for a while before doing upgrade, until next patch is released
(I mean full release of JumboPatch#1).
I did an upgrade from 4.0B to 4.0D, but know still about some big security
holes, which were not fixed yet. Others before applying the pre-patch had
AdvFS crashes (probably fixed in that pre-patch, but who knows).
---
"Allen, Mark R (PBD)" <Mark.Allen_at_pbdir.com>
Not any help, but I'm also keenly interested since we're looking at 4.0D
for Y2K as well.
Looking forward to your summary. :)
---
Chris Glenister <C.Glenister_at_cranfield.ac.uk>
I have upgraded some servers from DUnix 3.2d to 4.0b a
while ago. My experince was fine and everything went
smoothly.
If you do an updateinstall then you can go from 3.2c - 4.0d
relatively easily.
>From my installation, I went from 3.2d to 4.0 as per
instructions in the manual, then you apply the patches to
get from 4.0 to 4.0d for example.
As for the firmware, I always upgrade that last, once the
operating system has installed. Then I configure the server
if required.
My only problem was changing the root partition to be 128MB
instead of 64MB, because this is too small to perform and
upgrade install on and is a good idea with DUnix growing in
size.
I did not want to have to reconfigure the server from
scratch so I normally do an install update.
>From my experience the upgrade route works well and
preserves all my personal config files.
---
Bill Carlson <wcarlson_at_beasys.com>
Read all the release note on the ADVFS if you use that. After 3.2c I
had lots of problems with Advfs .
---
Robert L. McMillin <rlm_at_syseca-us.com>
Do the new installation. My advice:
0) Backup everything. Twice if you're paranoid.
1) Repartition the root/usr disk if needed. Older 3.2 systems had
smaller root partitions; 128 MB is now recommended (vs 64 MB
previously).
2) Install 4.0D new. This will save you much grief if you do this
instead of going 3.2C -> 3.2G -> 4.0 -> 4.0D (too many opportunities
for mistakes).
---
JEFFREY COWGILL <s018jxc_at_discover.wright.edu>
I upgraded from 3.2g to 4.0b last year and used the automated upgrade
path. This worked pretty well, leaving almost all my original settings in
place, however X was changed with the new common desktop environment being
installed also and I am planning on doing the upgrade to 4.0d on a extra
clean drive, then migrating my setup over to it, so I can have complete
control over what is installed and changed.
---
Michael James Bradford <mjbr_at_tdk.dk>
You are in for a busy weekend. I reckon that this upgrade path will take
approximately 12 hours, of which maybe 8 wil be sitting around waiting
for things to happen. Get use to seeing the messages "this may take some
time".
I will try to answer your questions based on my experiences (which do
not include NIS).
Firmware: There was a firmware CD with my 4.0D set (Update V5.0) and an
ECU diskette V1.11A (which you need if you have EISA). This has been no
problem, just boot from the CD, select update and sit back while it does
its thing. If you have EISA, from chevron prompt (>>>) use the command
"runecu" and follow each step.
The automated upgrade path works, but it takes a lot of time. There are
a few subsets that should be uninstalled before you start, as they halt
the update installation. See section 2.8.2.1 of the Installation Guide
for 4.0B or higher. If you used the dupatch method of applying patches,
you should uninstall the patches before you start the upgrade.
It is worth emptying the directory /var/adm/smlogs before you start and
in between each update step, reviewing the contents of the files, using
updadmin to check and delete the obsolete files, etc., and emptying the
directory again before continuing. This is because the files are
appended to and can get quite long.
You need to ensure you have a root partition that is at least 128Mb,
otherwise you end up having a lot of grief.
For you the update path is: 3.2C-->4.0-->4.0B-->4.0D-->patch. The patch
is available from ftp.service.digital.com/public/Digital_Unix/4.0D.
Once you are finished, check the license database (using lmf) to see if
you have an IMPLICIT USER license for OSF-USR. If so, delete it and
reset the license database.
If you have an other questions, please write to me and I will try to
answer them.
---
Claude SOMA - CNTS <soma_c_at_decus.fr>
I have tried once an upgrade from 3.2c to 3.2D-1 on an alpha server 2100.
1) look at the root partiton, if you are (say 98% full), the upgrade fail
and the system is completly UNUSABLE.
You must restart from CD-ROM.
(I don't remember exactly ,but I think the indication in the documentation
is not accurate)
2) Some body told me that when you do an upgrade, you MUST deinstall some
products (Decnet phase ??).
3) You MUST also deinstall patches.
(I think these patches are the culpid for me)
So if you do point 2 and 3, perhaps it's better to do a clean installation
from CD-ROM.
---
Norm Thomas <normt_at_ix.netcom.com>
Sorry so late but I just returned from a a 10 day, 9 system upgrade from
3.2C to 4.0D. I have 55 of these upgrades to complete.
We decided the fresh install route. We are not running C2 security. We
did back up several files and rebuilt others due to experience.
If you are still looking for more information or if I can be of any
assistance, please e-mail a note.
---
Regards,
Rich
/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ _ \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\
/_/ Richard A Bemrose /_\ Polymers and Colloids Group \_\
/_/ email: rb237_at_phy.cam.ac.uk /_\ Cavendish Laboratory \_\
/_/ Tel: +44 (0)1223 337 267 /_\ University of Cambridge \_\
/_/ Fax: +44 (0)1223 337 000 /_\ Madingley Road \_\
/_/ (space for rent) / \ Cambridge, CB3 0HE, UK \_\
/_/_/_/_/_/_/ http://www.poco.phy.cam.ac.uk/~rb237 \_\_\_\_\_\_\
"Life is everything and nothing all at once"
-- Billy Corgan, Smashing Pumpkins
Received on Tue Apr 28 1998 - 17:20:55 NZST
This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:37 NZDT