From owner-freebsd-questions Sat Feb 26 8:53:10 2000 Delivered-To: freebsd-questions@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 93ED137B6AC for ; Sat, 26 Feb 2000 08:52:51 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.12 #1) id 12OkSP-000Cau-00; Sat, 26 Feb 2000 16:52:41 +0000 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.12 #7) id 12OkSa-0003GC-00; Sat, 26 Feb 2000 16:52:52 +0000 Date: Sat, 26 Feb 2000 16:52:52 +0000 From: Ben Smithurst To: Mark Ovens Cc: freebsd-questions@freebsd.org Subject: Re: Why is my new kernel so big? Message-ID: <20000226165252.A294@strontium.scientia.demon.co.uk> References: <200002251624.LAA18500@benge.graphics.cornell.edu> <897eu4$pr3$1@bigeye.rhein-neckar.de> <20000226125745.A326@marder-1> <20000226135218.C98536@strontium.scientia.demon.co.uk> <20000226160008.A357@marder-1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000226160008.A357@marder-1> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Ovens wrote: > :) Yes, I'm thinking about cvsup'ing to 4.0 now. Have you done so, and > if so did you have any problems? Well, a few things went hideously wrong because I wasn't sure which order to do things in. I built a new kernel first, as I think you're supposed to because of the signal changes, but IIRC I had to move /modules out of the way so it couldn't load out of date modules which seemed to cause a panic. Then I screwed up the devices in /dev which is a bit of a pain to fix when you can't mount the root filesystem read/write (fsdb was useful for me though). Whatever you do, you'll probably do a better job that I did. :-) Basically, I think you need to something like: . build new kernel, install it, mv /modules /modules.old, reboot. (Make sure you compile support into the kernel for anything you previously used a module for.) . cd /usr/src/sbin/mknod; make all install clean (needed for MAKEDEV to work) . buildworld . mv /dev /dev.old mkdir /dev cd /dev cp /usr/src/etc/MAKEDEV . sh MAKEDEV all MAKEDEV any disks, e.g. sh MAKEDEV ad0s1 ad0s1a etc. remake any symlinks, e.g. mouse -> cuaa0, modem -> cuaa1, whatever. . changes disks in /etc/fstab and /etc/rc.conf from wd to ad, but keep a copy so you can put the old copy back with fsdb if things get screwed. . installworld, reboot. #include You should probably make a backup before starting, in case it goes hideously wrong. If you get to a point where you can't mount root read/write, you may be able to use fsdb to fix some things. Good luck, and don't blame me if things go wrong. ;-) -- Ben Smithurst / ben@scientia.demon.co.uk / PGP: 0x99392F7D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message