Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 08 Nov 1998 18:37:55 -0800
From:      "George W. Dinolt" <george.w.dinolt@lmco.com>
To:        Mike Smith <mike@smith.net.au>
Cc:        freebsd-current@FreeBSD.ORG, rnordier@nordier.com
Subject:   Re: Boot Loader question
Message-ID:  <36465583.E523F26E@lmco.com>
References:  <199811070750.XAA00452@dingo.cdrom.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Mike and Robert:

Many thanks for your responses to my message.
Mike Smith wrote:
> ...
> Ok.  Have you considered something like this:
> 
>   set choice=1
>   echo "1 - FreeBSD 2.2"
>   echo "2 - FreeBSD-current"
>   read -t 10 -p "Select >>" choice
>   set currdev=disk${choice}s1a:
>   source /boot/boot.conf2
> 
> in the default boot.conf, and then the 'real' boot instructions in
> /boot/boot.conf2?

I have taken your suggestion and a have a version which boots off of wd0
(my first disk) and takes the appropriate default action when I don't
type something in. Many thanks.

> ...
> However, to help you we need to know *what* the error is.

After the latest patches available via CTM (src-cur.3611) 
with the following "Id's"
$Id: boot1.s,v 1.4 1998/11/05 20:52:25 rnordier Exp $
$Id: boot2.c,v 1.13 1998/10/27 20:16:36 rnordier Exp $

I create a floppy with the following set of commands:

fdformat /dev/fd0.1440
disklabel -w -r fd0 fd1440
disklabel -B -b /boot/boot1 -s /boot/boot2 /dev/fd0
newfs rfd0 fd1440
mount /dev/fd0 /floppy
mkdir /floppy/boot
cp /boot/{boot1,boot2,loader} /floppy/boot
cd /floppy
echo boot/loader  > boot.config

When I boot from this floppy I get the error message:

Read error
Hit return to reboot:

If I follow the instructions, the floppy light goes on briefly and the
"Hit return..." message is reprinted on a new line. 

If I remove the floppy and hit return (error messages still on screen),
I get my usual 

F1 ...
F2 ...
F3 ...

messages and everything works as expected, that is I can boot.

Robert Nordier wrote:
...
>Since you use floppies, and get reproducible errors now, it'd be great
>if you'd undertake to test the new bootblocks and let us now if the
>problem has been resolved.
...

Glad to help. Unfortunately, I live behind a very restrictive firewall
and get my updates via CTM so I am usually a day or so behind the direct
CVS paths. I will keep you posted.

Regards, 
George Dinolt

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36465583.E523F26E>