Date: Wed, 08 Jun 2005 15:24:39 -0500 From: Paul Schmehl <pauls@utdallas.edu> To: freebsd-questions@freebsd.org Subject: Re: Editing the boot menu Message-ID: <B2EC37C39F9F5B22D56ED00E@utd59514.utdallas.edu> In-Reply-To: <5ef8c2f00506081229384d1be8@mail.gmail.com> References: <0DF7FF668F71A2B85D47F59B@utd59514.utdallas.edu> <5ef8c2f00506081229384d1be8@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--On Wednesday, June 08, 2005 16:29:22 -0300 Jos=E9 de Paula Rodrigues=20
<espinafre@gmail.com> wrote:
> On 6/8/05, Paul Schmehl <pauls@utdallas.edu> wrote:
>> When you use FreeBSD's boot manager, you get a menu like this at bootup:
>>
>> F1 DOS
>> F2 FreeBSD
>> F3 Linux
>> F4 ??
>> F5 Drive 1
>>
>> Default: F2
>>
>> Is there a way to edit the list? Or is that fixed when boot manager is
>> installed and not configurable?
>>
>> By edit, I mean, for example, change F4 ?? to F4 MyOS.
>>
>
> man boot0cfg
>
I *thought* it would go without saying that I had already read man =
boot0cfg.
Obviously, I missed the part where you edit the menu. Wanna give me a =
hint?
uname -imr
5.4-RELEASE i386 GENERIC
boot0cfg -v /dev/ad4
# flag start chs type end chs offset size
1 0x00 0: 1: 1 0x07 1023:254:63 63 204796557
2 0x80 1023:255:63 0xa5 1023:254:63 204796620 283482990
version=3D1.0 drive=3D0x80 mask=3D0xf ticks=3D182
options=3Dpacket,update,nosetdrv
default_selection=3DF2 (Slice 2)
The options for boot0cfg are:
-B Install the `boot0' boot manager. This option causes MBR code =
to
be replaced, without affecting the embedded slice table.
I don't need to install it.
-b boot0
Specify which `boot0' image to use. The default is =
/boot/boot0
which will use the video card as output, alternatively
/boot/boot0sio can be used for output to the COM1 port. (Be
aware that nothing will be output to the COM1 port unless the
modem signals DSR and CTS are active.)
I don't need to specify the boot image.
-d drive
Specify the drive number used by the PC BIOS in referencing =
the
drive which contains the specified disk. Typically this will=20
be
0x80 for the first hard drive, 0x81 for the second hard drive,
and so on; however any integer between 0 and 0xff is =
acceptable
here.
I don't need to specify the drive.
-f file
Specify that a backup copy of the preexisting MBR should be=20
writ-
ten to file. This file is created if it does not exist, and
replaced if it does.
I don't need to make a backup copy.
-m mask
Specify slices to be enabled/disabled, where mask is an =
integer
between 0 (no slices enabled) and 0xf (all four slices=20
enabled).
The correct slices are already enabled. The system boots fine to either =
OS.
-o options
A comma-separated string of any of the following options may =
be
specified (with ``no'' prepended as necessary):
The default options are being used, and I see no reason to change them.
packet Use the disk packet (BIOS INT 0x13 extensions)=20
interface,
as opposed to the legacy (CHS) interface, when doing=20
disk
I/O. This allows booting above cylinder 1023, but
requires specific BIOS support. The default is
`nopacket'.
setdrv Forces the drive containing the disk to be referenced
using drive number definable by means of the -d =
option.
The default is `nosetdrv'.
update Allow the MBR to be updated by the boot manager. (The
update Allow the MBR to be updated by the boot manager. (The
MBR may be updated to flag slices as `active', and to
save slice selection information.) This is the=20
default;
a `noupdate' option causes the MBR to be treated as=20
read-
only.
-s slice
Set the default boot selection to slice. Values between 1 and =
4
refer to slices; a value of 5 refers to the option of booting
from a second disk.
The default slice is determined by the last boot. I see no reason to=20
change that.
-t ticks
Set the timeout value to ticks. (There are approximately 18.2
ticks per second.)
The timeout is set to 10, and I see no reason to change that.
-v Verbose: display information about the slices defined, etc.
Self-explanatory.
So where is the switch that I use to edit the menu?
Paul Schmehl (pauls@utdallas.edu)
Adjunct Information Security Officer
University of Texas at Dallas
AVIEN Founding Member
http://www.utdallas.edu/ir/security/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B2EC37C39F9F5B22D56ED00E>