Lines Matching full:init

80 same reason you can't kill the init process; rather than having special code
96 checks to see if rootfs contains a file "init", and if so it executes it as PID
97 1.  If found, this init process is responsible for bringing the system the
99 any).  If rootfs does not contain an init program after the embedded cpio
101 to locate and mount a root partition, then exec some variant of /sbin/init
117   - The program run by the old initrd (which was called /initrd, not /init) did
118     some setup and then returned to the kernel, while the init program from
119     initramfs is not expected to return to the kernel.  (If /init needs to hand
120     off control it can overmount / with a new root device and exec another init
128     stdin/stdout/stderr to the new /dev/console, and exec the new init.
158   file /init initramfs/init.sh 755 0 0
165 two example "file" entries expect to find files named "init.sh" and "busybox" in
228 archive into rootfs before trying to run /init.
266 program as init, and test it under an emulator like qemu (www.qemu.org) or
279   gcc -static hello.c -o init
280   echo init | cpio -o -H newc | gzip > test.cpio.gz
285 "init=/bin/sh".  The initramfs equivalent is "rdinit=/bin/sh", and it's
319    extracted in init/initramfs.c.  All three together come to less than 26k
348 not contain an /init program.  The fallback is legacy code, there to ensure a