On Tue, 4 Oct 2011 14:32:51 -0700 Canek Peláez Valdés <can...@gmail.com> wrote:
> On Tue, Oct 4, 2011 at 2:24 PM, Grant Edwards > <grant.b.edwa...@gmail.com> wrote: > > On 2011-10-04, Canek Pel??ez Vald??s <can...@gmail.com> 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. > > > > I know. What I don't understand is the statement that grub2 calls > > (or connects to) the init system. > > > >> That's the init= command line in the kernel. > >> > >> The bootloader calls an operating system. The init system (if at > >> all) that the OS uses doesn't matter: so if you have an operating > >> system, any bootloader should be able to boot it (bearing things > >> like being able to understand the filesystem etc.) > > > > I know how bootloaders like LILO and grub-legacy work. What I don't > > understand is the statement that grub2 is somehow aware of the > > booted OS's init system. > > Oh. The configuration file of GRUB2 is autogenerated, and this means > that the init=systemd has to be passed to the kernel line. > > In that sense, GRUB2 is "aware" of it. Possibly what you meant to say is that grub2 is not aware of the OS but the grub2 installer does. Like grub and lilo before it, the installer is a Linux app; and can figure out the correct kernel parameters to use by examining the file system -- Alan McKinnnon alan.mckin...@gmail.com
