On Tuesday, 4. October 2011 14:14:24 Canek Peláez Valdés wrote: > On Tue, Oct 4, 2011 at 2:02 PM, Grant Edwards <grant.b.edwa...@gmail.com> wrote: > > On 2011-10-04, Canek Pel??ez Vald??s <can...@gmail.com> wrote: > >> On Tue, Oct 4, 2011 at 1:50 PM, Grant Edwards <grant.b.edwa...@gmail.com> wrote: > >>> On 2011-10-04, Canek Pel??ez Vald??s <can...@gmail.com> wrote: > >>>>>> That it's not true. It connects to whatever init system do you > >>>>>> have > >>>>>> (OpenRC, SysV, systemd, Upstart), > >>>>> > >>>>> I'm curious: what if you don't have one? ??I use grub-legacy to > >>>>> boot > >>>>> stuff other than Unix. > >>>> > >>>> When I said "it connects", I mean "calls". The same way it calls > >>>> whatever thingy Window uses. > >>> > >>> Right. ??And what about non-windows, non-Unix systems that don't > >>> have > >>> any thingy to call? > >> > >> Then you don't have an operating system. > > > > Yes, I do. > > 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? > Regards. Best, Michael
