mkimage-profiles/features.in/services/config.mk

use/services: sub/rootfs
	@$(call add_feature)
	@$(call xport,DEFAULT_SERVICES_ENABLE)
	@$(call xport,DEFAULT_SERVICES_DISABLE)
	@$(call xport,SERVICES_ENABLE)
	@$(call xport,SERVICES_DISABLE)

# some presets

use/services/ssh: use/services use/net
	@$(call add,THE_LISTS,openssh)
	@$(call add,DEFAULT_SERVICES_ENABLE,sshd)
initial rootfs subprofile and services feature This subprofile is akin to THE_* variables family: the configuration bits and script hooks sitting there influence whatever chroot is declared to be the user facing one in the end, whether it comes from vm image or live subprofile. The services feature ought to be a changeset of its own which would be based on rootfs and become the base for ve/vm changes but I chose to just do it atomically; some pre-existing duplicates are pruned now. 2013-05-28 12:51:36 +04:00			`use/services: sub/rootfs`
			`@$(call add_feature)`
			`@$(call xport,DEFAULT_SERVICES_ENABLE)`
			`@$(call xport,DEFAULT_SERVICES_DISABLE)`
			`@$(call xport,SERVICES_ENABLE)`
			`@$(call xport,SERVICES_DISABLE)`

			`# some presets`

net, services: in Soviet Russia... ...net uses services, not services use net. That is, "network" is a service that needs to be enabled by the now-existing mechanism of "services" feature, don't be fooled by "network services" here. 2013-06-25 21:59:47 +04:00			`use/services/ssh: use/services use/net`
			`@$(call add,THE_LISTS,openssh)`
initial rootfs subprofile and services feature This subprofile is akin to THE_* variables family: the configuration bits and script hooks sitting there influence whatever chroot is declared to be the user facing one in the end, whether it comes from vm image or live subprofile. The services feature ought to be a changeset of its own which would be based on rootfs and become the base for ve/vm changes but I chose to just do it atomically; some pre-existing duplicates are pruned now. 2013-05-28 12:51:36 +04:00			`@$(call add,DEFAULT_SERVICES_ENABLE,sshd)`