From: Kris Rusocki <kszysiu@xxxxxxxxxx>
Now that binfmt_script is configurable, explain yet another possible
cause of boot failure (a script w/CONFIG_BINFMT_SCRIPT != y).
Signed-off-by: Kris Rusocki <kszysiu@xxxxxxxxxx>
---
Documentation/init.txt | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/Documentation/init.txt b/Documentation/init.txt
index 535ad5e..8c6af4f 100644
--- a/Documentation/init.txt
+++ b/Documentation/init.txt
@@ -29,8 +29,9 @@
E) make sure the binary's architecture matches your hardware.
E.g. i386 vs. x86_64 mismatch, or trying to load x86 on ARM hardware.
In case you tried loading a non-binary file here (shell script?),
- you should make sure that the script specifies an interpreter in its shebang
- header line (#!/...) that is fully working (including its library
+ you should make sure that your kernel supports script execution
+ (CONFIG_BINFMT_SCRIPT=y) and the script specifies an interpreter in its
+ shebang header line (#!/...) that is fully working (including its library
dependencies). And before tackling scripts, better first test a simple
non-script binary such as /bin/sh and confirm its successful execution.
To find out more, add code to init/main.c to display kernel_execve()s
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
