| 1 |
On Tue, 04 Oct 2011 23:33:34 +0200, Michael Schreckenbauer wrote: |
| 2 |
|
| 3 |
> > Then any boot loader will need to call something to start it. |
| 4 |
> > Understand this: any Linux/Unix init system (systemd, SysV, Upstart, |
| 5 |
> > OpenRC) is simply a program... that the Linux kernel itself executes. |
| 6 |
> > That's the init= command line in the kernel. |
| 7 |
> |
| 8 |
> Correct, the *kernel* executes it. |
| 9 |
> |
| 10 |
> Quoted from an earlier mail in this thread: |
| 11 |
> |
| 12 |
> "That it's not true. It connects to whatever init system do you have |
| 13 |
> (OpenRC, SysV, systemd, Upstart)" |
| 14 |
> |
| 15 |
> The kernel executes the initsystem, the initsystem takes care of the |
| 16 |
> rest. Care to explain, why grub2 needs to connect to (or call) the |
| 17 |
> initsystem? |
| 18 |
|
| 19 |
The confusion is caused by using grub to describe two different modes of |
| 20 |
operation. the bootloader itself does not need access to anything but the |
| 21 |
kernel and the initramfs , if used. The grub program, run from Linux to |
| 22 |
set up the bootloader, does need access to your filesystem to be able to |
| 23 |
do its job. That is not required for booting, which is why the code is |
| 24 |
not in /boot. |
| 25 |
|
| 26 |
The GRUB2 bootloader works in much the same way as the old one, with the |
| 27 |
menu entry format being quite similar too. The difference is in the |
| 28 |
automation stuff that non-genkernel or other distro users wouldn't be |
| 29 |
interested in anyway. |
| 30 |
|
| 31 |
|
| 32 |
-- |
| 33 |
Neil Bothwick |
| 34 |
|
| 35 |
If you consult enough experts, you can confirm any opinion. |
Archives