Graham Christensen 64dd9c1d6a stage-2: parameterized systemd executable ... This lets users do sneaky things before systemd starts, and permanently affect the environment in which systemd runs. For example, we could start systemd in a non-default network namespace by setting the systemdExecutable to a wrapper script containing: #!/bin/sh ip netns add virtual touch /var/run/netns/physical mount -o bind /proc/self/ns/net /var/run/netns/physical exec ip netns exec virtual systemd _note: the above example does literally work, but there are unresolved problems with udev and dhcp._		2020-07-14 13:18:14 -04:00
..
activation	specialisation: replace nesting with named configurations	2020-04-12 08:12:50 -04:00
boot	stage-2: parameterized systemd executable	2020-07-14 13:18:14 -04:00
etc	environment.etc: fix typo	2020-03-09 12:01:41 +01:00