Re: [PATCH 4/3] start the global /sbin/init with 0,0 special pids

2007-11-27 Thread Eric W. Biederman
Pavel Emelyanov <[EMAIL PROTECTED]> writes: > Eric W. Biederman wrote: >> Oleg Nesterov <[EMAIL PROTECTED]> writes: >> >>> As Eric pointed out, there is no problem with init starting with sid == pgid >>> == 0, and this was historical linux behavior changed in 2.6.18. >>> >>> Remove kernel_init()-

Re: [PATCH 4/3] start the global /sbin/init with 0,0 special pids

2007-11-27 Thread Pavel Emelyanov
Eric W. Biederman wrote: > Oleg Nesterov <[EMAIL PROTECTED]> writes: > >> As Eric pointed out, there is no problem with init starting with sid == pgid >> == 0, and this was historical linux behavior changed in 2.6.18. >> >> Remove kernel_init()->__set_special_pids(). >> >> This change and the prev

Re: [PATCH 4/3] start the global /sbin/init with 0,0 special pids

2007-11-27 Thread Eric W. Biederman
Oleg Nesterov <[EMAIL PROTECTED]> writes: > As Eric pointed out, there is no problem with init starting with sid == pgid > == 0, and this was historical linux behavior changed in 2.6.18. > > Remove kernel_init()->__set_special_pids(). > > This change and the previous change in daemonize() mean tha

[PATCH 4/3] start the global /sbin/init with 0,0 special pids

2007-11-27 Thread Oleg Nesterov
As Eric pointed out, there is no problem with init starting with sid == pgid == 0, and this was historical linux behavior changed in 2.6.18. Remove kernel_init()->__set_special_pids(). This change and the previous change in daemonize() mean that /sbin/init does not need the special "session != 1"