From owner-freebsd-alpha  Tue Jun  8 12:14:51 1999
Delivered-To: freebsd-alpha@freebsd.org
Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125])
	by hub.freebsd.org (Postfix) with ESMTP id E5B5C14C12
	for <alpha@FreeBSD.ORG>; Tue,  8 Jun 1999 12:14:48 -0700 (PDT)
	(envelope-from ken@panzer.plutotech.com)
Received: (from ken@localhost)
          by panzer.plutotech.com (8.9.3/8.8.5) id NAA30292;
          Tue, 8 Jun 1999 13:14:43 -0600 (MDT)
From: "Kenneth D. Merry" <ken@plutotech.com>
Message-Id: <199906081914.NAA30292@panzer.plutotech.com>
Subject: Re: kern.bootfile...
In-Reply-To: <199906081902.XAA35913@arc.hq.cti.ru> from Dmitrij Tejblum at "Jun 8, 1999 11:02:56 pm"
To: tejblum@arc.hq.cti.ru (Dmitrij Tejblum)
Date: Tue, 8 Jun 1999 13:14:43 -0600 (MDT)
Cc: alpha@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Dmitrij Tejblum wrote...
> > Well, here's what happens with that patch:
> > 
> > {subway:/usr/home/ken:2:0} sysctl -a |grep kernel
> > kern.bootfile: //kernel.test
> > 
> > netstat, etc., works okay, probably because the leading slash is discarded.
> > 
> > And here's what happens without the patch, when kernel.test2 is booted:
> > 
> > {subway:/usr/home/ken:1:0} sysctl -a |grep kernel
> > kern.bootfile: /kernel
> 
> Uh, I am even more confused. When I tried to use bootinfo.booted_kernel to get 
> the
> name of the kernel, it did contain only the last component and didn't contain 
> any
> slash. I have had a code that deal with all the cases I could imagine, but 
> decided
> to not commit it as it looks too large for such a simple job.
> 
> > 
> > Could it have something to do with the boot loader?  /boot/loader is from
> > my buildworld on Saturday, but one thing I've noticed is that the text that
> > comes up before the boot loader prompt ("FreeBSD/alpha SRM disk boot,
> > Revision 0.1") is dated September, 1998.  So it sort of seems like
> > /boot/loader may not be what is used here..
> 
> Perhaps. It seems like boot1 used /boot/boot2 at some point. I don't have this file
> here :-).

Hmm, I think that explains it:

{subway:/boot:3:130} ls -la
total 326
drwxr-xr-x   3 root  wheel     512 Jun  5 23:26 ./
drwxr-xr-x  18 root  wheel    1024 Jun  8 12:27 ../
-r-xr-xr-x   1 root  wheel    7352 Jun  5 23:25 boot1*
-r-xr-xr-x   1 root  wheel   82432 Sep 24  1998 boot2*
drwxr-xr-x   2 root  wheel     512 Mar 26 15:24 defaults/
-r-xr-xr-x   1 root  wheel   97608 Jun  5 23:26 loader*
-r--r--r--   1 root  wheel    9916 Apr 22 14:07 loader.help
-r-xr-xr-x   1 root  wheel  117232 Jun  5 23:26 netboot*

boot2 is from last September.  I just did a 'disklabel -B da1' and now
everything works just fine.  The unpatched kernel shows the right kernel
name:

{subway:/usr/home/ken:5:0} sysctl kern.bootfile
kern.bootfile: /kernel.test2

On a loader-related note, does anyone have any idea why I can't seem to
type a question mark in the loader?  I don't have any problems typing
question marks once FreeBSD is booted, but in the loader, I seem to
always come up with '/', whether or not I hold down the shift key at the
same time..

And another weird thing -- when I do a 'shutdown -h' and drop the machine
(a 433au) into the SRM prompt, all the key mappings seem to be screwed up,
and I can't type anything useful.

Ken
-- 
Kenneth Merry
ken@plutotech.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message