From: Jacques Gelinas (jack_at_solucorp.qc.ca)
Date: Tue Dec 04 2001 - 15:59:55 EST
On Tue, 4 Dec 2001 15:47:52 -0500, Christian wrote
> why not provide a real init to the vserver? that would make rebooting more
> sane (we dont need the reboot daemon), the vserver would be more
> compatible/consistent.
I will experiment running a real init there.
One issue is that orphan process are reparent to process 1. I think this
is hardcoded in the kernel. Changing this behavior to reparrent to the
security context 'first process' might make init more standard.
Another trick would be to map process number 1 to the security context
first process. So doing
kill -HUP 1
would work. Internally, the kernel would change it to whatever IP.
> how2: store an offset for all pid's of a security-context, so that the
> vservers init becomes Pid 1 its decendants (and itself). (does this
> require big kernel changes? i don't assume)
This is also possible.
Having one init per vserver has some advantages
-Makes the runlevel concept available in vservers as well
-Make inittab respawn process available
It does not make the reboot available. A reboot needs to stop everything
and start over. The rebootmgr server is still needed to clean up any
remaining tasks, including the init itself.
The first step would be to try a real init with the kernel ctx-4 kernel to
see how far we go with this.
---------------------------------------------------------
Jacques Gelinas <jack_at_solucorp.qc.ca>
vserver: run general purpose virtual servers on one box, full speed!
http://www.solucorp.qc.ca/miscprj/s_context.hc
This archive was generated by hypermail 2.1.4 : Mon Aug 19 2002 - 12:01:00 EDT