From nobody@FreeBSD.ORG  Mon Jun 12 01:43:58 2000
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 93D7537C981; Mon, 12 Jun 2000 01:43:58 -0700 (PDT)
Message-Id: <20000612084358.93D7537C981@hub.freebsd.org>
Date: Mon, 12 Jun 2000 01:43:58 -0700 (PDT)
From: pekkas@netcore.fi
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@FreeBSD.org
Subject: if /boot.config is present, user intervention is required at boot time.
X-Send-Pr-Version: www-1.0

>Number:         19215
>Category:       misc
>Synopsis:       if /boot.config is present, user intervention is required at boot time.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Jun 12 01:50:00 PDT 2000
>Closed-Date:    Mon Jun 12 07:57:08 PDT 2000
>Last-Modified:  Mon Jun 12 08:10:00 PDT 2000
>Originator:     Pekka Savola
>Release:        3.4-STABLE
>Organization:
-
>Environment:
FreeBSD loghost1 3.4-STABLE FreeBSD 3.4-STABLE #1: Wed Feb 16 21:30:36 EET 2000     root@loghost1:/usr/src/sys/compile/LOGHOST  i386

This box has been updated from 2.2.6 -> 2.2.8 -> 3.2-R -> 3.4-S with cvsup.
>Description:
I queried about this in freebsd-questions, but since no one replied, 
I doubt this is a real feature.

If you put anything in /boot.config, user intervention will be required
at boot time; for example, putting "kernel -P" or "0:wd(0,a)/kernel -P" 
in /boot.config yields the following:
----
>How-To-Repeat:
put e.g. 'kernel' in /boot.config.
>Fix:


>Release-Note:
>Audit-Trail:

From: Ruslan Ermilov <ru@sunbay.com>
To: pekkas@netcore.fi
Cc: bug-followup@FreeBSD.org
Subject: Re: misc/19215: if /boot.config is present, user intervention is required at boot time.
Date: Mon, 12 Jun 2000 13:11:58 +0300

 On Mon, Jun 12, 2000 at 01:43:58AM -0700, pekkas@netcore.fi wrote:
 > 
 > This box has been updated from 2.2.6 -> 2.2.8 -> 3.2-R -> 3.4-S with cvsup.
 > 
 > If you put anything in /boot.config, user intervention will be required
 > at boot time; for example, putting "kernel -P" or "0:wd(0,a)/kernel -P" 
 > in /boot.config yields the following:
 
 >  >> FreeBSD/i386 BOOT
 >  Default: 0:wd(0,a)
 >  
 >  boot:
 >  No
 >  
 And you also upgraded your boot blocks with `disklabel -B', right?
 
 -- 
 Ruslan Ermilov		Oracle Developer/DBA,
 ru@sunbay.com		Sunbay Software AG,
 ru@FreeBSD.org		FreeBSD committer,
 +380.652.512.251	Simferopol, Ukraine
 
 http://www.FreeBSD.org	The Power To Serve
 http://www.oracle.com	Enabling The Information Age
 

From: Pekka Savola <pekkas@netcore.fi>
To: Ruslan Ermilov <ru@sunbay.com>
Cc: bug-followup@FreeBSD.org
Subject: Re: misc/19215: if /boot.config is present, user intervention is
 required at boot time.
Date: Mon, 12 Jun 2000 13:25:07 +0300 (EEST)

 > >  >> FreeBSD/i386 BOOT
 > >  Default: 0:wd(0,a)
 > >  
 > >  boot:
 > >  No
 > >  
 > And you also upgraded your boot blocks with `disklabel -B', right?
 
 Yes.  No effect. :(
 
 -- 
 Pekka Savola                    "Tell me of difficulties surmounted, 
 Pekka.Savola@netcore.fi          not those you stumble over and fall"
 
 
State-Changed-From-To: open->closed 
State-Changed-By: ru 
State-Changed-When: Mon Jun 12 07:57:08 PDT 2000 
State-Changed-Why:  
Pilot error (extraneous blank lines at the end of /boot.config). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=19215 

From: Ruslan Ermilov <ru@sunbay.com>
To: Pekka Savola <pekkas@netcore.fi>
Cc: bug-followup@FreeBSD.org
Subject: Re: misc/19215: if /boot.config is present, user intervention is required at boot time.
Date: Mon, 12 Jun 2000 17:53:34 +0300

 On Mon, Jun 12, 2000 at 04:07:32PM +0300, Pekka Savola wrote:
 > > Hmm, that is strange.  Let's check that your bootblocks are OK.
 > > Please execute the following commands, and send me /tmp/boot.tgz.
 > > 
 > > # dd if=/dev/wd0c of=/tmp/boot1 count=1
 > > # dd if=/dev/wd0c of=/tmp/boot2 skip=1 count=15
 > > # tar zcvf /tmp/boot.tgz /tmp/boot[12] /boot/boot[12]
 > > 
 > > Please also send me the output of the fdisk(8) command.
 > 
 Your bootblocks are correct, but your /boot.config (which I do not
 have) is incorrect (and that is why I asked you to send me one!!).
 Please remove any extra blank lines from your /boot.config and
 everything will be fine.  What really is going on here is that
 2nd stage of boot blocks (boot2) attempts to load "" from your
 root filesystem, fails to do so, and reports `No ""' (where "'s
 are invisible).  Make sure that `wc -l /boot.config' returns the
 value of 1.
 
 
 Cheers,
 -- 
 Ruslan Ermilov		Oracle Developer/DBA,
 ru@sunbay.com		Sunbay Software AG,
 ru@FreeBSD.org		FreeBSD committer,
 +380.652.512.251	Simferopol, Ukraine
 
 http://www.FreeBSD.org	The Power To Serve
 http://www.oracle.com	Enabling The Information Age
 
>Unformatted:
 >> FreeBSD/i386 BOOT
 Default: 0:wd(0,a)
 
 boot:
 No
 
 >> FreeBSD/i386 BOOT
 Default: 0:wd(0,a)         
 ----
 Note 'No' there.  You _have_ to type 'kernel', 'kernel -P' , 
 '/boot/loader', or whatever you want by hand.  Boot process will
 remain forever waiting for user input there otherwise.
 
 Deleting /boot.config file restores the automatic booting w/ boot loader.
 
 I'm happy to do some tests on this if you like.
