Talk:Arch boot process
Boot loader vs boot manager
There is a template:expansion at Arch boot process#boot loader. My understanding of what Wikipedia:Booting#Modern_boot_loaders means, is that the topic should have been titled boot manager, not boot loader. I find the first sentence of the topic,
not accurate. In my view, the boot loader is actually part of the BIOS or UEFI. One of their jobs is to load a boot manager. The boot manager is the
- piece of software started, but not included, within the BIOS or UEFI
It is their follower. In general, I think the boot loader job is to get the machine into a predefined state, a state that requires no intimate knowledge of the specific hardware in order to finalize the boot process. Therefore, a general boot manager, such as those mentioned, can finalize, or manage the final steps, of the boot process. Contrast that with initiating the boot process, where the bios/uefi programmers, and hardware manufactures, must coordinate with each other. In other words, a boot loader is Wikipedia:Booting#First-stage boot loader, and a boot manager is Wikipedia:Booting#Second-stage boot loader. In the past, Linux tried to include the boot loader. Due to the exceeding complexity it had gone to, partially because the lack of the exact details of each hardware, Linux dropped that ability.
Alternatively, if one wonders what exactly does the the boot manager manage, one might imagine that the BIOS or UEFI call the boot manager, which, in turn, calls the boot loader. With this line of thinking, the boot loader is the last step to run by the boot manager. That is, the boot loader is the one that actually loads the OS. In the case of a simple boot manager, such as EFISTUB, the boot loader is its main component. Where as more complex boot managers deal with more requirements.
- I doubt there is established naming. One can use UEFI/GPT standard, but who says it is ultimate spec regarding the boot (in addition, there are other platforms)? Your proposed naming (implicitly assuming) to call BIOS/UEFI as 'boot loader/manager' is strange - I rarely see that it is called in such way (although, I acknowledge that UEFI spec may call itself in a such way). When people say 'boot loader/manager' they usually mean 'piece of software started by BIOS/UEFI, which starts operating system and does potentially other things, not limited to: starting other boot loaders, checking mem, etc.'. One reason why people do not consider BIOS/UEFI firmware as 'boot loader/manager' is that they have no choice is selecting it. My proposal is to leave everything as it is. If there is no difference between names 'boot loader/manager', then one name should be used consistently across the article. Alternatively, one can use UEFI/GPT spec naming approach.
- P.S. I doubt that even if you collect technical evidence supporting your position, you can make significant change because Arch wiki (like other Arch projects) is somewhat authoritarian. There is one and only one right idea - those, which belongs to wiki maintainers. If you have different opinion, you are out of luck. If you insists on your opinion, you will be called newbie, technically unsophisticated person who is not able to understand intelligence of wiki maintainers (forum mods, TUs, depending on the context). I personally gave up on editing this wiki because of this reason. --Mxfm (talk) 07:04, 13 January 2019 (UTC)
- Nice rant.
- When I added the Template:Expansion, I had the definition from https://www.rodsbooks.com/efi-bootloaders/index.html in mind. Basically a boot loader loads the kernel, while a boot manager executes the EFISTUB kernel as an EFI application and the kernel does all the boot related stuff itself. -- nl6720 (talk) 10:32, 13 January 2019 (UTC)