A quick grep in the tree shows the following existing cases (wrapped for line length).
$ git grep -E \ 'keyword .*(lxc|systemd-nspawn|vserver|prefix|openvz|uml|jail|xen)' sys-apps/kmod/files/kmod-static-nodes-r1: keyword -lxc -systemd-nspawn sys-fs/eudev/files/udev-postmount: keyword -vserver -lxc sys-fs/zfs/files/zfs-0.6.1-gentoo-openrc-dependencies.patch: keyword -lxc -openvz -prefix -vserver sys-fs/zfs/files/zfs-0.6.5-fix-openrc-scripts.patch: keyword -lxc -openvz -prefix -vserver sys-power/nut/files/nut.powerfail.initd: keyword -jail -lxc -openvz -prefix -uml -vserver -xenu -timeout The only one of those I can speak knowledgeably about is sys-power/nut. That script signals the UPS to cut the power, and is intended to be the very very last shutdown script ever called on a box (so it has a sleep forever bit at the end). Does it make sense in a container? That depends on how the container is configured... it's got the right details for the container parent's UPS, then you certainly don't want it to fire. If it had details to tell the parent to just terminate it, then it would be correct. Rather than replacing all of the system-specific keywords, can we make 'container' into an alias that expands to the full list of known container types? That way, if there is an init script that is specific to some container type, it would still be usable. One hypothetical case that does come to mind is some container-type-specific setup script. Say there is 'foocontainerFS' and it requires special mount parameters during the startup of the container, or the container wants some special daemon to be running... both of these cases could use: keywords -containers foocontainer -- Robin Hugh Johnson Gentoo Linux: Developer, Infrastructure Lead, Foundation Trustee E-Mail : robb...@gentoo.org GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
signature.asc
Description: Digital signature
