BIOS is the traditional boot method, and is well-supported by Debian. There are several choices for the placement of the boot code. Common practice is for it to be placed in the MBR at the beginning of the boot disk. However, if there are multiple operating systems already installed (especially Microsoft Windows), this replaces the installed bootloader with the one common to Linux. This is generally not a problem, since the installation and update process searches for other operating systems and includes the ability to boot them as an alternative in the boot menu.
, The current bootloader for Debian on Intel is called GRUB2, although 'If:;.> other, older loaders exist and may be installed as an alternative.
However, there are occasions where the original, non-Linux bootloader is preferred. For example, some Windows installations won't update properly ifa non-Windows bootloader is installed. Inthis case, the Linux boot code can be placed at the beginning of the Linux boot partition rather than the MBR at the beginning of the drive, where the non-Linux bootloader can usually find it and offer it as an alternative on its boot menu.
The problem of Windows updates when using the Linux GRUB2 bootloader is quite complex. The issue seems to occur primarily with major Internet Explorer version upgrades, and the reasons remain unclear, at least in any discussions and bug reports I've been able to find. Adding to the problem is the occasional report of inconsistent recognition of Linux boot partitions by the Windows loader. There seems to be no hard-and-fast guideline as to which Windows installations will experience problems and which will not. The only certain way to know is to try it, and that requires patience, good backups, and a willingness to start over ifit doesn't work.
So, ifyou are planning to use a dual or multiboot layout that includes Windows, and you don't have the time, patience, and determination to actually try all the alternatives, the answer comes down to the following practical considerations:
- Can you live without a major version upgrade to Internet Explorer?
- Can you run Windows as a VM instead of as part of a dual or multiboot system?
- Will your Windows bootloader recognize the Linux boot partition?
Many users never upgrade major versions of Internet Explorer, and are perfectly satisfied with security and feature updates to their current version. If this works for you, then proceed with the default placement in the MBR. Ifyou absolutely must have the ability to upgrade major Internet Explorer versions, consider running Windows as a VM rather than as part of a dual or multiboot system. Ifyou do not wish to do so (usually because of virtual hardware compatibility or licensing issues), then go with installing the Linux bootloader at the beginning of the Linux partition. Recent versions of Windows (since Vista) are pretty good about recognizing the Linux boot partition and adding it to the boot menu.
Best practice is to use the default placement in the MBR. Only ifyou truly need the original bootloader should you place the Linux boot code at the beginning of the Linux boot partition and, ifnecessary, configure the non-Linux bootloader to include it in the boot menu, ifit doesn't do so automatically.