Problem with PPID

[Denys Vlasenko]

On Sunday 04 November 2007 17:54, Marc Blumentritt wrote:
> Denys Vlasenko schrieb:
> > On Sunday 04 November 2007 12:07, Marc Blumentritt wrote:
> > 
> > mount -t proc proc /proc
> > ps -a > /ps_init_data
> 
> Now I have these results:
> root at mediamachine $ cat /ps_init_data
> PID   USER     COMMAND
>     1 root     init
>     2 root     [kthreadd]
>     3 root     [migration/0]
>     4 root     [ksoftirqd/0]
>     5 root     [events/0]
>     6 root     [khelper]
>    34 root     [kblockd/0]
>    35 root     [kacpid]
>    36 root     [kacpi_notify]
>   124 root     [ksuspend_usbd]
>   127 root     [khubd]
>   129 root     [kseriod]
>   144 root     [pdflush]
>   145 root     [pdflush]
>   146 root     [kswapd0]
>   147 root     [aio/0]
>   148 root     [jfsIO]
>   149 root     [jfsCommit]
>   150 root     [jfsSync]
>   151 root     [xfslogd/0]
>   152 root     [xfsdatad/0]
>   824 root     [kpsmoused]
>   833 root     init
>   834 root     /bin/sh /sbin/rc.init
>   836 root     ps -A
> 
> Is this the expected result, that init starts first a child of itself,
> which then starts my init script rc.init?

Apparently yes. It happens in init/init.c, in this function:

static pid_t run(const struct init_action *a)

I think it should be either explained in detail in the comments,
or simplified.
--
vda