Random

Needs some sort of persistent state of chroots. We don't have a persistent process for the lifetime of the chroot. UNLESS we run a daemon.

Thus we want a daemon. This will also ease the handling of auto-upgrades for a chroot (copy the chroot, try dist-upgrade, sync back if no errors). Locking for chroot will then be controlled through that daemon. Capabilities will be dropped by the daemon as far as possible after launch. Vserver has its own forked copy of the control daemon.

Config in /etc/multibuild/root. Currently no possibility to overwrite anything by the user.

Config should define sources.list entries.

Hook design like builder? * chroot update * build package * yield shell with pipes (no network, except ssh+http, insert ssh_known_hosts for e.g. *.debian.org). Must use a pty for filtering ANSI codes.

Authentication per UNIX-Socket (SCM_CREDENTIALS). Authorization in extra layer if neccessary.

Process/Thread per active root, commands can only be passed through the control daemon.

FD-Passing, SCM_RIGHTS

SOCK_DGRAM sockets?

hooks:

• authentication
• authorization
• base create (handles updates too)
• active create
• base remove
• active remove