Date: Thu, 5 Feb 1998 05:11:17 -0800 (PST) From: wefa@unicom.talkline.de To: freebsd-gnats-submit@FreeBSD.ORG Subject: misc/5659: 2.2.5 Install doesn't copy kernel Message-ID: <199802051311.FAA16538@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 5659
>Category: misc
>Synopsis: 2.2.5 Install doesn't copy kernel
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Feb 5 05:20:00 PST 1998
>Last-Modified:
>Originator: Christoph Weber-Fahr
>Organization:
O.tel.o. Communications
>Release: 2.2.5
>Environment:
FreeBSD hektor.otelo-call.de 2.2.5-RELEASE FreeBSD 2.2.5-RELEASE #0: Thu Jan 29
22:07:42 CET 1998 root@hektor.otelo-call.de:/usr/src/sys/compile/HEKTOR i38
6
>Description:
Installed 2.2.5 over an existing 2.2.2-System.
Sine I had rescued /etc and other config stuff manually,
I didn't use the 'upgrade' option but did a custom install
without newfs. Install recognised existing partitions and
acknowleged an existing system ('won't make new devices').
Install completed without error messages.
After reboot system came up with old custom-compiled 2.2.2
kernel, and quite some error messages (unserstandably :-)
The root fs contained (among others)
- the old 2.2.2 /kernel
- a new 2.2.5 /kernel.GENERIC
- a zero length file /kernel.install (or somesuch)
>How-To-Repeat:
see above
>Fix:
Copying the .GENERIC to /kernel did the trick.
I've checked the errata.txt on the ftp sites and found
nothing on that topic.
If that's not a bug but a feature, install should
refuse to proceed at some point or give some
kind of error message on it.
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802051311.FAA16538>