Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 30 Jan 1999 00:13:19 +1000 (EST)
From:      Andrew Kenneth Milton <akm@zeus.theinternet.com.au>
To:        jkh@zippy.cdrom.com (Jordan K. Hubbard)
Cc:        stable@FreeBSD.ORG
Subject:   Re: When to transition to 3.0-STABLE..  NOT NOW!
Message-ID:  <199901291413.AAA02953@zeus.theinternet.com.au>
In-Reply-To: <82789.917504214@zippy.cdrom.com> from "Jordan K. Hubbard" at "Jan 27, 99 10:16:54 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
+----[ Jordan K. Hubbard ]---------------------------------------------
| If you're running 3.0-RELEASE or 2.2.x-SOMETHING and you're thinking
| of upgrading to 3.0-STABLE at this time, I thought I would just send a
| quick heads-up which says simply: "Don't!"

Well I did, since I had committed resources to doing it before this
warning had arrived, so I can provide some feedback to that process.

This isn't to incite the mobs to upgrade, I'd say if you can
wait until Mid-Feb, then do so, but, if you really have to, then
this might help you out a little.

It will also hopefully provide some more background for those
people working on the upgrade procedure.

I had a 2.2.5-Release system, with no sources other than kernel
sources installed.

I'd tried months ago to upgrade from 2.2.S to 3.0.C to no avail,
so I took along my 3.0.SNAP CDs (which I knew how to upgrade from)
in case anything went tragically wrong.

If you don't backup, well, you get what you deserve.

I had allowed 6 hours for this upgrade, not including the
actual aout-to-elf-build which I did beforehand.

Things to check:-

Do you have DES passwords or do you have the MD5(?) ones only?
If you have DES passwords you may be locked out since the DES
libs didn't get built for me, I had to build these by hand and
then change the symlinks in /usr/lib (which all appeared to be
symlinks to themselves). There is an auth.conf file that contains
some stuff, but, doesn't look too relevant (I'm not running K5), 
and still wouldn't make those cyclic symlinks work any better.

Do you want to (re)build things from the ports dir? You will want
to update your ports tree. And if you want to rebuild stuff to
get your machine up (i.e. from single user mode), then you'll 
want to do this beforehand (and prefetch the distfiles).

You *will* want mergemaster. It's handy d8) Get and install this
before doing anything else.

I cvsupped the source on Tuesday, and then updated the tree again
on Wednesday.

I started the aout-to-elf-build Wednesday night at let it run overnight.
That built to completion without problem.

aout-to-elf-install does pretty well with fixing your kernel config
to cope with the new syscons config, however, there were a few
options that I had that no longer exist:-

pseudo-device   log             #Kernel syslog interface (/dev/klog)
options         BOUNCE_BUFFERS
options         CHILD_MAX=128
options         OPEN_MAX=128

also if you have an IDE CDROM in your config you'll need to change
wcd to acd since even with ATAPI and ATAPI_STATIC defined the
new kernel would probe the CDROM and discover it, but would simply
say:

Jan 29 18:58:50 mercury /kernel: wdc1: ATAPI CD-ROMs not configured

You will want to update your kernel config file before you do
an aout-to-elf-install.

During this process ldconfig -R failed a lot all the way through during
I assume the move-aout-libs stage. This didn't seem to actually break
anything.

If you're running pppd, the rassen frassen /etc/ppp/pap-secrets file 
has changed formats again. and dns1/dns2 has been replaced with
msdns

If you're running a name-server, you will want to run
named-bootconf < named.boot > named.conf and remove any
named flags from rc.conf unless your files are in a non-standard place.

Other than this everything went pretty smoothly

I don't have sendmail on this box, so I can't talk about upgrading
that stuff.

It took me five hours, but, most of that time was first tracking why
ipfw was locked up (nameserver was not running due to named.boot/
named.conf changeover) that included lots of rebooting and fsck'ing,
the crypt problem, and then trying to workout why pppd was hosed.

Anyway hopefully this will help the adventurous or the cursed, and
hopefully help out the upgrade team at least a little.

-- 
Totally Holistic Enterprises Internet|  P:+61 7 3870 0066   |  Andrew
The Internet (Aust) Pty Ltd          |  F:+61 7 3870 4477   |  Milton
ACN: 082 081 472                     |  M:+61 416 022 411   |72 Col .Sig
PO Box 837 Indooroopilly QLD 4068    |akm@theinternet.com.au|Specialist

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901291413.AAA02953>