From cagney@tpgi.com.au Thu Mar 18 19:27:12 1999
Return-Path: <cagney@tpgi.com.au>
Received: from andrew1.lnk.telstra.net (andrew1.lnk.telstra.net [139.130.51.121])
	by hub.freebsd.org (Postfix) with ESMTP id 4C1B9153EC
	for <FreeBSD-gnats-submit@freebsd.org>; Thu, 18 Mar 1999 19:27:06 -0800 (PST)
	(envelope-from cagney@tpgi.com.au)
Received: (from cagney@localhost)
	by andrew1.lnk.telstra.net (8.9.2/8.8.8) id OAA63427;
	Fri, 19 Mar 1999 14:26:48 +1100 (EST)
	(envelope-from cagney)
Message-Id: <199903190326.OAA63427@andrew1.lnk.telstra.net>
Date: Fri, 19 Mar 1999 14:26:48 +1100 (EST)
From: Andrew Cagney <cagney@tpgi.com.au>
Reply-To: cagney@tpgi.com.au
To: FreeBSD-gnats-submit@freebsd.org
Subject: Notes on 2.2.8 -> 3.1 migration
X-Send-Pr-Version: 3.2

>Number:         10664
>Category:       docs
>Synopsis:       Notes on 2.2.8 -> 3.1 migration
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Mar 18 19:30:00 PST 1999
>Closed-Date:    Tue Dec 7 15:04:07 PST 1999
>Last-Modified:  Tue Dec  7 15:04:43 PST 1999
>Originator:     Andrew Cagney
>Release:        FreeBSD 3.1-RELEASE i386
>Organization:
Ye ol' disorganized FreeBSD user
>Environment:

root@b1.cygnus.com# uname -a
FreeBSD b1.cygnus.com 3.1-RELEASE FreeBSD 3.1-RELEASE #3: Thu Mar 18 19:43:54 EST 1999     cagney@b1.cygnus.com:/usr/src/sys/compile/B2pcm  i386

>Description:

Just FYI.


* How was it?

trivial[]; ok[]; annoyances[X]; problems[]; disaster[]; you'll be
hearing from the lawyers[].

(2.2.7 -> 2.2.8 was ``trivial'').


* What problems?


* /etc/rc.firewall wasn't restored:

A new version of that file was installed in /etc instead of keeping
around my existing (and highly customized version).  Just FYI.  


* ldconfig and aout->elf shared libraries:

Yes the notes warned about this one :-) I suspect that further
preparation is needed on my part - but then I didn't have much to go
on.

When the system comes up /etc/defaults/rc.conf sets
``ldconfig_paths_aout'' to "/usr/lib/compat/aout /usr/X11R6/lib/aout
/usr/local/lib/aout".  Unfortunately on an ill prepared ex 2.2.8 system
this isn't the case.

Perhaps a note bringing the admins attention to this one.  The admin
could then: re-arrange their shared libraries in readiness; just
append the old paths to the above.


* New bind (named), no compatibility mode, no obvious doco:

Another big jump.  Bind changes and there isn't a quick/easy way to
revert to the old bind while the new config file is being built.
(Fortunately the new bind does come up in a vaguely sane state :-).

The real problem was finding any documentation on this new beastie so
that I could get my server working again.


* Kernel.

Hey the new man pages are useful!  Migrating my kernel config to the
new sources didn't prove too hard.  I just had to grub through
config/{GENERIC,LINT} and device man pages (bktr was very clear) to
determine what I needed to add/delete.

No real surprises with this one.


* A ``X-Kern-Developer'' category?

``Full binaries and doc, kernel sources, X Window system''.
Just a suggestion :-)


* Should the ports/src directories be moved aside?

Just some defensive thoughts (I did this by hand).  Should the upgrade
process at least warn the user that the /usr/ports and /usr/src
directories are about to be trashed.  (Since they contain both old and
new stuff they need replacing.

For ports, what I did was saved /usr/ports/distfiles but trashed
everything else.



>How-To-Repeat:

Try doing another 2.2.8 -> 3.1 migration

>Fix:
	
If this is all I've got to complain about things can't be going too
bad.  Well done.

>Release-Note:
>Audit-Trail:

From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
To: cagney@tpgi.com.au
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: docs/10664: Notes on 2.2.8 -> 3.1 migration
Date: 19 Mar 1999 04:48:22 +0100

 Andrew Cagney <cagney@tpgi.com.au> writes:
 > * New bind (named), no compatibility mode, no obvious doco:
 > 
 > Another big jump.  Bind changes and there isn't a quick/easy way to
 > revert to the old bind while the new config file is being built.
 > (Fortunately the new bind does come up in a vaguely sane state :-).
 
 If you have the sources installed, there is a script for converting
 named.boot to named.conf:
 
 /usr/src/contrib/bind/bin/named/named-bootconf.pl
 
 I guess perhaps it should be copied to /etc/named or somesuch place by
 make installworld.
 
 DES
 -- 
 Dag-Erling Smorgrav - des@flood.ping.uio.no
 

From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
To: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Cc: cagney@tpgi.com.au, FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: docs/10664: Notes on 2.2.8 -> 3.1 migration
Date: 19 Mar 1999 04:49:32 +0100

 Dag-Erling Smorgrav <des@flood.ping.uio.no> writes:
 > If you have the sources installed, there is a script for converting
 > named.boot to named.conf:
 
 Uh, my bad: it is actually installed as /usr/sbin/named-bootconf.
 
 DES
 -- 
 Dag-Erling Smorgrav - des@flood.ping.uio.no
 

From: Andrew Cagney <cagney@cygnus.com>
To: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Cc: cagney@tpgi.com.au, FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: docs/10664: Notes on 2.2.8 -> 3.1 migration
Date: Fri, 19 Mar 1999 15:02:55 +1100 (WET)

 Excerpts from mail: 19-Mar-99 Re: docs/10664: Notes on 2... Dag-Erling
 Smorgrav@floo (272)
 
 > Dag-Erling Smorgrav <des@flood.ping.uio.no> writes:
 > > If you have the sources installed, there is a script for converting
 > > named.boot to named.conf:
 
 > Uh, my bad: it is actually installed as /usr/sbin/named-bootconf.
 
 Ah, thanks!  Something to add to the upgrade notes.  Too late in my case
 but useful all the same.
 
 	enjoy,
 		Andrew
 
State-Changed-From-To: open->closed 
State-Changed-By: chris 
State-Changed-When: Tue Dec 7 15:04:07 PST 1999 
State-Changed-Why:  
Enjoy FreeBSD! 
(This PR is not a bug report, so it does not need to remain open) 
>Unformatted:
