Hi Steve, On Sat, Apr 18, 2015 at 12:02 PM, Steve Litt <sl...@troubleshooters.com> wrote:
> On Sat, 18 Apr 2015 00:08:54 -0400 > Jude Nelson <jud...@gmail.com> wrote: > > > > The init program in example/initramfs/init goes into > > /usr/share/initramfs-tools/init, not /sbin/init :) The initramfs's > > init script is fundamentally different from the init program > > in /sbin. That also explains your inability to reboot. > > > > Basically, when the bootloader loads the initramfs, the kernel mounts > > it as the root device and starts /sbin/init. /sbin/init, in turn, > > runs the script at /init (which you can see from the initramfs shell > > with "ls /"), which is copied into the initramfs image by the > > update-initramfs and mkinitramfs tools from the > > file /usr/share/initramfs-tools/init. > I had misspoken here--as Laurent and Isaac pointed out, the kernel will load /init as PID 1 in the initramfs. This script in turn exec's the "real" init process from the root device (/sbin/init). I'm sorry if I caused confusion--I will be more careful in the future to fact-check myself. Thanks, -Jude
_______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
