Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 22 Jan 1999 09:03:09 +0200 (SAT)
From:      Robert Nordier <rnordier@nordier.com>
To:        peter.jeremy@auss2.alcatel.com.au (Peter Jeremy)
Cc:        current@FreeBSD.ORG
Subject:   Re: Booting from 2nd IDE [Re: Experiences with aout-to-elf and new bootblocks]
Message-ID:  <199901220703.JAA15837@ceia.nordier.com>
In-Reply-To: <99Jan22.110737est.40377@border.alcanet.com.au> from Peter Jeremy at "Jan 22, 99 11:08:12 am"

next in thread | previous in thread | raw e-mail | index | archive | help
Peter Jeremy wrote:

> Mark Blackman <tmb@rcru.rl.ac.uk> wrote:
> >FWIW, I've done it under 2.2.7 by
> >
> >1) installing booteasy on both wd0 *AND* wd2
> >2) altering the boot.config to
> >   1:wd(2,a)kernel
> 
> This works for an a.out 3.0 kernel, but the old bootloader can't handle
> ELF kernels, so this isn't a usable solution.

The new boot blocks, installed by

    disklabel -B $DRIVE

do handle (both a.out and) ELF kernels, despite looking very similar
to the old a.out-only ones.  The idea is to provide a fallback
means of booting a kernel in either format.

So using a /boot.config statement like the above (or hitting any
key before seeing the /boot/loader prompt, to get the old "boot:"
prompt instead), is a recommended workaround for any temporary
/boot/loader problems.

--
Robert Nordier

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?199901220703.JAA15837>