Bootloader options during installation

[Apatewna]

This is not a problem but a mere question.

Suppose I want to install PCBSD on a new PC. During the installation the bootloader screen gives options of "install on MBR" and "do not install botloader". What happened to the the second choice "Install typical bootloader"?

I always select this second choice whenever I build a FreeBSD server for example, since there is no need to select another operating system by pressing F1, F2 etc.

I can load the default mbr (/boot/mbr) using fdisk, but I am more interested at the reason this option was left outside since I can already think of one use for it.

[antik]

This is not a problem but a mere question.

Suppose I want to install PCBSD on a new PC. During the installation the bootloader screen gives options of "install on MBR" and "do not install botloader". What happened to the the second choice "Install typical bootloader"?

I always select this second choice whenever I build a FreeBSD server for example, since there is no need to select another operating system by pressing F1, F2 etc.

I can load the default mbr (/boot/mbr) using fdisk, but I am more interested at the reason this option was left outside since I can already think of one use for it.

I think that "install on MBR" and "Install typical bootloader" is the same. FreeBSD bootloader can be installed only to MBR because you can't install loader into partition as with Linux due to totally different partition meanings and technology.

[Apatewna]

"install on MBR" probably executes <boot0cfg> and writes /boot/boot0 to the MBR of the disk you specify. This means that you at least get a boot screen with "F1 Freebsd" option.

On the other hand "Typical bootloader" probably executes <fdisk> and writes /boot/mbr to the MBR of the disk you specify. This get you a direct boot of the operating system. It's a nice choice IMHO.

P.S. I have done this testing while trying to dual-boot PCBSD on the first physical disk and windows XP on the second physical disk. I ended up running boot0cfg targeting both disk and installing /boot/boot0.

http://forums.pcbsd.org/viewtopic.php?t ... light=dual (http://forums.pcbsd.org/viewtopic.php?t=3266&highlight=dual)

[TerryP]

When I setup the two FreeBSD installs here, the options we're to install a standard MBR to only boot FBSD (boots to the menu to select normal/safe/acpi disabled e.t.c. boot), install boot loader (F1, F2 e.t.c), or leave the MBR alone and use your own bootloader.

Install MBR=Only FreeBSD
Boot loader=Multi-OS want this loader
No touch=Have a bootloader or want a diffrent one.

PC-BSD GUI installer gives choice of option 2 or 3, manually fdisking I think gives you the option of 1,2, and 3.

[Apatewna]

Option 1 in FreeBSD is "Install BSD bootloader on MBR"

% man boot0cfg
The boot0cfg utility optionally installs the `boot0' boot manager on the
specified disk; and allows various operational parameters to be configured.

The Options
-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.)

Option 2 in FreeBSD is "Install basic bootloader on MBR"
%man fdisk
fdisk -- PC slice table maintenance utility

Options are:
-b bootcode
Get the boot code from the file bootcode. Default is /boot/mbr.

Option 3 is "Do not touch the MBR"

PCBSD misses Option 2

[TerryP]

Yes, I shall go buttout and eat a sandwhich so I can stop making a fool of myself.