Skip to main content

bootloader - primary and secondary boot loaders


From http://www.ibm.com/developerworks/library/l-bootload/index.html



Boot loaders are usually configured in one of two ways: either as a primary boot loader or as a secondary boot loader.


Primary boot loaders are where the first stage of the boot loader is installed on the MBR (per the previous description).


Secondary boot loaders are where the first stage of the boot loader is installed onto a bootable partition.


A separate boot loader must then be installed into the MBR and configured to pass control to the secondary boot loader.



Should "first" in "Secondary boot loaders are where the first stage of the boot loader is installed onto a bootable partition" be "second" instead?


Where is the secondary boot loader stored? Not in MBR where the primary boot loader is stored?


What is "a separate boot loader" in the last sentence? Is it the primary or secondary boot loader?


is the primary boot loader the same concept as the initial program loader (IPL, mentioned in the same link)?



Due to the very small amount of data the BIOS can access, most boot loaders load in two stages. In the first stage of the boot, the BIOS loads a part of the boot loader known as the initial program loader, or IPL. The IPL interrogates the partition table and subsequently is able to load data wherever it may exist on the various media. This action is used initially to locate the second stage boot loader, which holds the remainder of the loader. The second stage boot loader is the real meat of the boot loader; many consider it the only real part of the boot loader. This contains the more disk-intensive parts of the loader, such as user interfaces and kernel loaders. These user interfaces can range from a simple command line to the all-singing, all-dancing GUIs.



Thanks!



Answer



There is an ambiguity in that text actually. Primary boot loader doesn't mean the first stage of a boot loader, and secondary boot loader doesn't mean the second stage of a boot loader.


First stage of a boot loader is the program resides in MBR data which holds partition information and capability to handle very basic disk I/O operations those cannot accomplish to fully load the O.S since MBR boot loader code size is limited to 448-bytes for standart MBR records (lower for spesific O.S implementations, since partition table holds 4*16-Bytes)


First stage of the boot loader's job is to simply load the second stage which now nows the O.S spesifics and it has much more code space. As far as I remember, NTFS second boot loader has 16 512-bytes sectors to load O.S kernel, 8-KBytes.


Primary and secondary terms come in where there are multiple O.S.es to choose to boot. Each O.S has its boot loader that has first and second stages, each boot loader should start from stage one since the primary boot laoder in MBR shouldn't be expected to know about spesifics of the second stages in every boot loader.


Second stages are stored on the beginning of the partition itself which is called VBR, Volume Boot Record.


When there is one O.S to boot, MBR program (IPL) is the first stage and VBR program is the second stage. When there are multiple O.Ss, MBR program becomes the first stage of the primary boot loader, that stage know there are some code in some partition which is second stage to fully load the whole menu and options, and loads it. That second stage knows about the partitions which has VBR, and continues with VBR, now VBR became secondary boot loader.


Yes, I said "each boot loader should start from stage one since the primary boot laoder in MBR shouldn't be expected to know about spesifics of the second stages in every boot loader.". It is why VBR code also has MBR code in itself, too. Windows VBR codes have it.


Comments

Post a Comment

Popular Posts

keyboard - Is there any utility/method to change Windows key bindings to type rare chars to currently empty bindings?

I'm currently typing this post with my windows XP machine and (Spanish) keyboard, and I'd like to add some extra symbols to my text. I could open the "char map" windows utility, look for the desired symbols, and paste them. But I'd like something quickier. For example, when I'm using my OSX Mac at work, I can easily add a ©, ™, ® or similar symbols, just pressing some weird ALT-GR + G / H / J, key combinations. In my (Spanish) keyboard mapping, these combinations are empty, as they don't produce any char at all, which, on the other hand, is perfectly normal and desirable. So, I thought: Why couldn't I add some extra key mappings on top of my currently empty ALT-GR + G/J/H Keys in my Spanish keyboard, and thus, being able to quickly type these special symbols? So that's my question: Is there any utility/method to achieve that effect under windows? (My version is XP). I've even googled this for some time but no luck. I've been a long term Hot...
Post a Comment
Read more

virtualization - How to select paravirtualization interface in VirtualBox?

Given a windows 8 host system (Intel Core i5) and a Linux Fedora host, I would like to determine the optimal setting for the paravirtual interface. Options are none Default Legacy minimal Hyper-V KVM This page suggest the selection is only based on the guest system: The biggest change in VirtualBox 5.0 is the introduction of paravirtualization support, bringing higher performance and time-keeping accuracy to supported guest operating systems (Hyper-V on Windows and KVM on Linux). Is that correct? Answer The VirtualBox Manual , in the section titled Paravirtualization providers explains very clearly when each should be used (emphasis added): Minimal: Announces the presence of a virtualized environment. Additionally, reports the TSC and APIC frequency to the guest operating system. This provider is mandatory for running any Mac OS X guests. KVM: Presents a Linux KVM hypervisor interface which is recognized by Linux kernels starting with version 2.6.25. VirtualBox's implementati...
Post a Comment
Read more

Desktop reboots itself on sleep or hibernate

I have been using an ASUS M2NPV-VM motherboard for main home desktop workstation, operating Windows Vista x64. This computer has right from day one not been able to enter hibernate or standby; after Windows performs its final actions and brings the machine down, it would automatically revive itself for a reboot. Updating to the second latest BIOS (1201)has not helped (the latest BIOS revision would induce video refresh problems rendering it unusable). I have been reading related discussions on incidents similar to mine to no avail of a true workable solution. They appear to be more speculative guesses rather than actual knowledge on the inner workings of motherboard hardware. Does anybody have any electronic engineering experience on PC energy-saving standards to provide a more informed opinion how to go about getting this to work? More stories: this motherboard could not even reboot properly the first thing i used it. It was due to refresh rate of the onboard GPU, which had no influe...
Post a Comment
Read more

security - How is Linux not prone to viruses, malware and those kinds of things?

How is Linux protected against viruses? This question was a Super User Question of the Week . Read the blog entry for more details or contribute to the blog yourself Answer Well, it factually is not... it's just less subject to hackers developing viruses that target Linux systems. Consumer grade computers usually run on Windows and thus, when targeting a wide audience, Windows is the way to go. Don't misunderstand Linux and viruses, there definitely ARE Linux viruses. Some distros have additional protection layers such as SELinux (See here ) in Ubuntu for example. Then there's the default firewall and the fact that alien files don't automatically have permission to be executed. Specific execution permission has to be granted before execution is possible. (See here ) Then there are several other factors that make Linux a hard place to be for viruses usually non-root users on linux systems have no to little executable files at their disposal that would allow for virus...
Post a Comment
Read more