From owner-freebsd-questions Sat Aug 21 20: 2:35 1999 Delivered-To: freebsd-questions@freebsd.org Received: from nisser.com (n2000039.telekabel.chello.nl [212.187.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 928E015129 for ; Sat, 21 Aug 1999 20:02:31 -0700 (PDT) (envelope-from roelof@nisser.com) Received: from nisser.com (roelof [10.0.0.2]) by nisser.com (8.9.2/8.9.2) with ESMTP id FAA05210 for ; Sun, 22 Aug 1999 05:01:06 +0200 (CEST) (envelope-from roelof@nisser.com) Message-ID: <37BF67F5.81917DA7@nisser.com> Date: Sun, 22 Aug 1999 05:01:09 +0200 From: Roelof Osinga Organization: eboa - engineering buro Office Automation X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-questions@FreeBSD.ORG Subject: Problems migrating from 3.1 to 3.2 via CVSup Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is something else compared to migrating within the 3.1 branche. In fact, in my case it didn't turn out as advertised at all. For starters the rebuild kernel wouldn't load: Booting [kernerl] /kernel text=0x131d0a elf_loadexec: archsw.readin failed can't load 'kernel' is what it complained about. Well, I had seen messages stating that one should start with rebuilding the GENERIC kernel in case of changed options and take it from there, so this didn't come as a total shock. However, other things did. Before reboot I did merge, manually, all changes in /etc, /dev et al. All except for the sendmail.cf which I saved for a rainy day. But when I finally found a kernel that would boot and connect to the 'Net I got my next surprise. It wouldn't load the rc's. I got things like "inetd: illegal option --w" and lots of complaints about "set -T" not being as legal as the script supposed. Finally there was in /etc/defaults/rc.conf an addition stating that natd resides in /sbin whereas in actuallity it resides in /usr/bin on my system. So I was forced to "boot" manually. Which is a problem if one has become used to having scripts doing the diry work. Still, I managed to bring the system up to a more or less operable state. In which process I discovered that several other things went awry as well. Most notably I do not have all man pages. The 3.2 migration did add the TCP wrappers but did not add the accompanying manpages. Bummer. Anyway, at this point I'm wondering how best to proceed. Clearly my system is out of whack, so how to whack it back again? What would be the best strategy to bring it back into shape. What to do and how to do it? If anyone knows, *please* advice. Roelof PS did try searching for clues, got lots and lots of references, none truly helpful alas. The best I could come up with was: http://x21.deja.com/getdoc.xp?AN=502545224&CONTEXT=935290767.1877737511&hitnum=0 which describes it as "not that hard". Well... is, too! Bah. -- Home is where the (@) http://eboa.com/ is. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message