From owner-freebsd-bugs  Sun Apr  9 13:20:14 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id NAA01309
          for bugs-outgoing; Sun, 9 Apr 1995 13:20:14 -0700
Received: (from gnats@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id NAA01301
          ; Sun, 9 Apr 1995 13:20:13 -0700
Date: Sun, 9 Apr 1995 13:20:13 -0700
Message-Id: <199504092020.NAA01301@freefall.cdrom.com>
From: uhclem%nemesis@fw.ast.com
Reply-To: uhclem%nemesis@fw.ast.com
To: freebsd-bugs
Subject: bin/315: Kernel and boot block don't agree on kernel name 	FDIV010
In-Reply-To: Your message of Sun, 9 Apr 95 13:07 CDT
	<m0ry1Ou-0004upC@nemesis.lonestar.org>
Sender: bugs-owner@FreeBSD.org
Precedence: bulk


>Number:         315
>Category:       bin
>Synopsis:       Kernel and boot block don't agree on kernel name 	FDIV010
>Confidential:   yes
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs (FreeBSD bugs mailing list)
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Apr  9 13:20:11 1995
>Originator:     Frank Durda IV
>Organization:
>Release:        FreeBSD 2.0.0-SNAP950322 i386
>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*

>Audit-Trail:
>Unformatted: