Re: Active slice, only for a next boot

[ Available lists | Index of freebsd-hackers | Month of May 2011 | Week of 31 May 2011 | Raw email | View thread | Wrap long lines | Reply | Tag ]
From
Peter Jeremy <peterjeremy@acm.org>
Date
31 May 2011 09:30:49
Subject
Re: Active slice, only for a next boot
Message-ID
20110531072346.GA56848@server.vk2pj.dyndns.org

In reply to
References to

[ Hide this part ]
On 2011-May-30 17:42:39 +0000, Dieter BSD <dieterbsd@engineer.com> wrote:
>A better approach is to be able to boot whatever slice you
>want without having to change the active slice.
>
>NetBSD can do this. The MBR puts up a menu of the bootable
>slices on the disk being booted. You can allow the timer
>to time out and boot the default. Or you can enter the number
>of the slice you want to boot. Or you can type a function key
>F1 F2 ... to boot a different disk, and it will load the MBR
>from that disk and run it. There is an alternative for keyboards
>without function keys.

So can FreeBSD - though only for MBR - this functionality doesn't seem
to have made it into the GPT bootcode.

>And it works great. Except that one of the 27 stages of boot
>code that FreeBSD uses INSISTS on booting the active slice,
>so you can tell the MBR to boot slice 3 and slice 3's boot
>code sees that slice 4 is active and boots slice 4.

Multibooting worked correctly when I last used it (a few years ago).
Have you raised this as a PR?

>RS-232 console + hardware modem + POTS = remote console

And even that doesn't fully work unless you have a serial-aware BIOS.

--
Peter Jeremy


[ Show this part (application/pgp-signature) ]

Elapsed time: 0.097 seconds