From owner-freebsd-questions  Tue May 11 17: 1:11 1999
Delivered-To: freebsd-questions@freebsd.org
Received: from modgud.nordicrecords.com (h21-168-107.nordicdms.com [207.21.168.107])
	by hub.freebsd.org (Postfix) with SMTP id BDDE614D4E
	for <freebsd-questions@freebsd.org>; Tue, 11 May 1999 17:01:05 -0700 (PDT)
	(envelope-from walton@nordicrecords.com)
Received: (qmail 12738 invoked by uid 65534); 12 May 1999 00:01:03 -0000
Date: 12 May 1999 00:01:03 -0000
Message-ID: <19990512000103.12736.qmail@modgud.nordicrecords.com>
From: Dave Walton <walton@nordicrecords.com>
To: Ilia Chipitsine <ilia@cgilh.chel.su>
Reply-To: Dave Walton <walton@nordicrecords.com>
Cc: freebsd-questions@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: IMP/PHP3 Imap webMail Program 1.99 beta
Subject: Re: can't find /boot/loader
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Quoting Ilia Chipitsine <ilia@cgilh.chel.su>:

> Does it help to ...
>  echo "load /kernel" > /boot/loader.rc

/boot/loader.rc contains:

  load /kernel
  load -t userconfig_script /boot/kernel.conf
  autoboot


>  or maybe
>  echo "1:wd(2,a)kernel" > /boot.config

Hmmm...  /boot.config doesn't exist.  During the boot process, I see:
  changing root device to wd0s1a
Would that mean that I need "0:wd(0,a)kernel" instead?

Anyway, boot(8) says that /boot.config is used to bypass the third stage of the 
new boot process.  What I really want to do is make the third stage run as it 
used to, and hopefully find out why it stopped working.

Dave


> 
> Regards, (с наилучшими пожеланиями,)
> 
>  Ilia Chipitsine (Илья Шипицин)
> 
> On 9 May 1999, Dave Walton wrote:
> 
> > Hello all,
> > 
> > I recently compiled a new kernel for a box running 3.1-R.  Ever since
> then, 
> > booting the machine results in the following error:
> > 
> > Disk error 0x1 (lba=0x10040)
> > No /boot/loader
> > 
> > That is followed by a 2.x-style "boot:" prompt.  Entering "-c" at that
> prompt 
> > allows me to manually adjust the configuration, after which booting
> proceeds 
> > normally.  /boot/loader and associated files do, in fact, exist.  Any
> ideas what
> > 
> > might be going on here?  (Please CC: me in replies so I'm sure to see
> it.)
> > 
> > Thanks,
> > Dave
> > 
> > 
> > 
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-questions" in the body of the message
> > 
> 
> 


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