Bug 19215

Summary:	if /boot.config is present, user intervention is required at boot time.
Product:	Base System	Reporter:	Pekka Savola <pekkas>
Component:	misc	Assignee:	freebsd-bugs (Nobody) <bugs>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	3.4-STABLE
Hardware:	Any
OS:	Any

Description Pekka Savola 2000-06-12 09:50:00 UTC

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.

Comment 1 Ruslan Ermilov 2000-06-12 11:11:58 UTC

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

Comment 2 Pekka Savola 2000-06-12 11:25:07 UTC

> >  >> 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"

Comment 3 Ruslan Ermilov 2000-06-12 15:53:34 UTC

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

Comment 4 ru freebsd_committer

2000-06-12 15:57:08 UTC

State Changed
From-To: open->closed

Pilot error (extraneous blank lines at the end of /boot.config).