On Wed, 5 Oct 2011 14:46:03 +0000 (UTC) Grant Edwards <grant.b.edwa...@gmail.com> wrote:
> > The *installer* portion of grub2 is aware of which pid#0 is running > > when it auto-creates the bootloader's configuration. That pid#0 is > > passed on to the kernel by the bootloader. > > OK. I that I understand. It seems a bit redundant to me: I've been > running Linux since the 0.99 days and never had to pass init= to a > kernel. But, I guess it won't hurt anything. It is indeed redundant and harmless. You no doubt already know the kernel's logic for launching the first userspace app - three paths are hardcoded and searched in sequence, first one found is launched. The third one is /sbin/init It makes for a wonderful prank, add "init=bin/bash" to someone's menu.lst and watch them get confused at next reboot :-) I suppose grub2 could search for and include a redundant init parameter for the sake of consistency with cases where a non-standard init was in use -- Alan McKinnnon alan.mckin...@gmail.com
