From nobody  Thu Feb  5 05:11:17 1998
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id FAA16538;
          Thu, 5 Feb 1998 05:11:17 -0800 (PST)
          (envelope-from nobody)
Message-Id: <199802051311.FAA16538@hub.freebsd.org>
Date: Thu, 5 Feb 1998 05:11:17 -0800 (PST)
From: wefa@unicom.talkline.de
To: freebsd-gnats-submit@freebsd.org
Subject: 2.2.5 Install doesn't copy kernel
X-Send-Pr-Version: www-1.0

>Number:         5659
>Category:       misc
>Synopsis:       2.2.5 Install doesn't copy kernel
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    jkh
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Feb  5 05:20:00 PST 1998
>Closed-Date:    Thu Jul 23 02:39:08 PDT 1998
>Last-Modified:  Thu Jul 23 02:39:30 PDT 1998
>Originator:     Christoph Weber-Fahr
>Release:        2.2.5
>Organization:
O.tel.o. Communications
>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.


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: hoek 
State-Changed-When: Thu Jul 23 02:28:42 PDT 1998 
State-Changed-Why:  
Damn.  I need sleep (5am!  Why am I doing this!?). 
State-Changed-From-To: closed->open 
State-Changed-By: hoek 
State-Changed-When: Thu Jul 23 02:29:36 PDT 1998 
State-Changed-Why:  
Never meant to closed 
Responsible-Changed-From-To: freebsd-bugs->jkh 
Responsible-Changed-By: hoek 
Responsible-Changed-When: Thu Jul 23 02:29:56 PDT 1998 
Responsible-Changed-Why:  
sysinstall doesn't, when doing the bin (or whatever) install, 
remove the old /kernel and replace it with one that is synced with 
the new bin dist. 

"Is this a feature or a bug?" 

I guess I always considered a feature, but from this PRs perspective, it 
can certainly be seen as a bug, too.  Jkh designed this thing, so only 
he can say for sure.  Once actually decided, I imagine it's pretty 
easy to fix or close the PR as approp. 
State-Changed-From-To: open->closed 
State-Changed-By: jkh 
State-Changed-When: Thu Jul 23 02:39:08 PDT 1998 
State-Changed-Why:  
Fixed in later 2.2.x releases.  The old kernel wasn't being properly 
chflags'd. 
>Unformatted:
