From nemesis!uhclem@fw.ast.com  Sun Apr  9 13:13:38 1995
Received: from relay1.UU.NET (relay1.UU.NET [192.48.96.5])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA01064
          for <FreeBSD-gnats-submit@freebsd.org>; Sun, 9 Apr 1995 13:13:34 -0700
Received: from ast.com by relay1.UU.NET with SMTP 
	id QQyktk25339; Sun, 9 Apr 1995 16:13:29 -0400
Received: from trsvax.fw.ast.com (fw.ast.com) by ast.com with SMTP id AA08868
  (5.67b/IDA-1.5 for uunet!freebsd.org!FreeBSD-gnats-submit); Sun, 9 Apr 1995 13:17:36 -0700
Received: by trsvax.fw.ast.com (/\=-/\ Smail3.1.18.1 #18.1)
	id <m0ry3FE-0000H1C@trsvax.fw.ast.com>; Sun, 9 Apr 95 15:06 CDT
Received: by nemesis.lonestar.org (Smail3.1.27.1 #18)
	id m0ry1Ou-0004upC; Sun, 9 Apr 95 13:07 CDT
Message-Id: <m0ry1Ou-0004upC@nemesis.lonestar.org>
Date: Sun, 9 Apr 95 13:07 CDT
From: uhclem%nemesis@fw.ast.com
Reply-To: uhclem%nemesis@fw.ast.com
To: FreeBSD-gnats-submit@freebsd.org
Cc: uhclem@nemesis.lonestar.org
Subject: Kernel and boot block don't agree on kernel name 	FDIV010
X-Send-Pr-Version: 3.2

>Number:         315
>Category:       bin
>Synopsis:       Kernel and boot block don't agree on kernel name 	FDIV010
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Apr  9 13:20:11 1995
>Closed-Date:    Sat Jun 24 08:33:38 PDT 1995
>Last-Modified:  Tue Nov 27 18:41:51 PST 2001
>Originator:     Frank Durda IV
>Release:        FreeBSD 2.0.0-SNAP950322 i386
>Organization:
>Environment:

SNAP-950322


>Description:

[FDIV010]

The boot block looks for a kernel named 386bsd (or 386bsd.old) rather
than kernel*.  

At first I thought I had downloaded the wrong floppy images, but a second
download of the files in SNAP-032295/floppies resulted in the same problems.

SNAP-021095 did not have this problem and searched for "kernel".


>How-To-Repeat:


>Fix:
	
Rename kernel or link to 386bsd will get around the problem of autobooting.

Hopefully we will switch back to the boot blocks we had in SNAP-950210
which thought the kernel was caller "kernel".

*END*

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: jkh 
State-Changed-When: Sat Jun 24 08:33:38 PDT 1995 
State-Changed-Why:  
caused by a SNAP not updating the boot block 
>Unformatted:



