Timeline for What can make passing init=/path/to/program to the kernel not start program as init?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 16, 2018 at 12:37 | comment | added | Ciro Santilli OurBigBook.com |
You must use rdinit when booting from ramdisk apparently: unix.stackexchange.com/a/430614/32558
|
|
| Feb 12, 2012 at 23:41 | vote | accept | Shawn J. Goff | ||
| Jan 31, 2012 at 5:21 | comment | added | Kyle Jones | The code I looked at (v3.2.2 I think) checked set ramdisk_execute_command if it was unset and then tried to run it, so you must not be that current. Too bad, because I didn't see anything else that would explain it. | |
| Jan 31, 2012 at 4:00 | comment | added | Shawn J. Goff |
Actually, it checks execute_command first, which comes from the kernel command line init= parameter. If it can't execute it, it prints a warning and tries to run init in various locations. This is in init/main.c in the function init_post(). I looked through the kernel printk messages and found the warning in my kernel's output, so now I have to figure out why it can't start /bin/sh or anything else that I try to start.
|
|
| Jan 31, 2012 at 2:35 | history | answered | Kyle Jones | CC BY-SA 3.0 |