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