From owner-freebsd-questions Mon Nov 24 12:05:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA29768 for questions-outgoing; Mon, 24 Nov 1997 12:05:03 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA29752 for ; Mon, 24 Nov 1997 12:04:59 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.7) with SMTP id MAA12904; Mon, 24 Nov 1997 12:04:52 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Mon, 24 Nov 1997 12:04:52 -0800 (PST) From: Doug White Reply-To: Doug White To: Neil Ludban cc: freebsd-questions@FreeBSD.ORG Subject: Re: 2.2.5 upgrade not replacing kernel In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 21 Nov 1997, Neil Ludban wrote: > Somebody posted a question a couple days ago wondering why the new > kernel's boot message said it was still the old version. After getting > 2.2.5 installed and working on my SCSI drive, I decided to upgrade the > 2.2.2 version on the old IDE drive. Here's what it did: > > # ls -l /IDE/kern* > -r-xr-xr-x 1 root wheel 1172726 Nov 21 09:40 /IDE/kernel > -rwxr-xr-x 1 root wheel 1457189 Oct 21 10:33 /IDE/kernel.GENERIC > -r-xr-xr-x 1 root wheel 1173041 Oct 20 12:21 /IDE/kernel.TIG1 > -rw-r--r-- 1 root wheel 0 Nov 21 09:51 /IDE/kernel.config > -r-xr-xr-x 1 root wheel 1173041 Oct 6 20:42 /IDE/kernel.old > -r-xr-xr-x 1 root wheel 1172726 Nov 21 09:12 /IDE/kernel.prev > > kernel and kernel.prev are identical, kernel.GENERIC is 2.2.5. The first > time I booted with -c, and it was using the old hardware configuration. > Let it finish booting, figured out it was the old kernel, then rebooted > using kernel.GENERIC. This is a known bug in sysinstall; it forgets to link the new /kernel. kernel.GENERIC is the new one, just copy it over. > 195 v0 D+ 0:00.03 mount /dev/sd0a /mnt > 196 v0 DV+ 0:00.01 mount /dev/sd0a /mnt > > After a minute or so, "ncr0: timeout ccb=50506000 (skip)" showed up on the > console. Having had enough errors for one day, I tried to reboot and got > "init: Some processes would not die; ps axl advised", then "Syncing > disks... done" (later found out it did not set the clean flag). Looks like those mount procs hung. Your SCSI disk wasn't happy? > Last question -- is it possible to do an install or upgrade from a SCSI > zip drive? I was unable to find a way to mount it. I forgot to try this when I swiped our spare Zip. I think it should work OK if the ZIP is either DOS-formatted or BSD-formatted. In the DOS case it should think it's a DOS hard disk and give you the option in DOS install. For the BSD case I think it should treat it as a UFS install. In both cases you must have the cart in the drive at boot time. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major