Firstly, a /linuxrc script can't be PID 1. Check the bottom of
do_basic_setup in init/main.c:
pid = kernel_thread(do_linuxrc, "/linuxrc", SIGCHLD);
Since do_basic_setup is already PID 1, /linuxrc won't be.
If you need /linuxrc to be PID 1, don't call it /linuxrc, but /sbin/init
Paul Powell wrote:
> This is a followup question to my previous question
> "Why isn't init at PID 1."
>
> Previoulsy I was calling init from within linuxrc.
> Linuxrc was a sash script, so the sash script
> supposedly had PID 1. Now I've removed the script and
> have a C program for linuxrc.
>
On Wed, Jan 31, 2001 at 11:23:38AM -0800, Paul Powell wrote:
> This is a followup question to my previous question
> "Why isn't init at PID 1."
Lots of stuff assumes that PID 0 is the idle task, and that PID 1 is init.
For example, the kernel disallows ptraceing of init, based on its pid of 1.
I
This is a followup question to my previous question
"Why isn't init at PID 1."
Previoulsy I was calling init from within linuxrc.
Linuxrc was a sash script, so the sash script
supposedly had PID 1. Now I've removed the script and
have a C program for linuxrc.
I'm still not running at PID 1 but
4 matches
Mail list logo