Hi Purushotham., 2015-07-29 8:28 GMT+02:00 purushi1 . <[email protected]>: > Hi Bartosz Golaszewski, > > If i disable CONFIG_INIT flag in busybox configuraton, Then Kernel Bootup > fails . > I get the following message : > > "Kernel panic - not syncing: No init found. Try passing init= option to > kernel. See Linux Documentation/init.txt for guidance. > Rebooting in 180 seconds. " > > > So tried passing an init option, with init=/usr/lib/systemd/systemd or > init=/usr/bin/bash. > Using either of the option i am able to boot without any kernel panics. > > Is this the right way? Please advice.
The kernel tries to find init in various locations (/sbin/init, /etc/init, /bin/init, etc.). If it can't execute any of those, then the kernel panics. You just removed Busybox init, so you are left without init process to load. One way to override kernel search is passing init= option as you did. You can put that option in the bootloader options and get done, or you can symlink systemd (or what you want to load) in /sbin/init so the kernel can find it in the "standard" location. HTH, Xabier Oneca_,,_ _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
