This duplicates sys-apps/baselayout so don't bother. Probably left over
from when baselayout wasn't properly installed with the 'build' use flag
to initialize the filesystem tree.
Remove the following unused users/groups:
- core-access
- polkituser
- pkcs11
- ipsec
- tor
- tcpdump
- debugd
- openvpn
- input
Add groups:
- docker (new group, for things like access to docker socket)
- systemd-journal (exists in sdk, not images. for journal log access)
- dialout (exists in sdk, required by default udev rules)
The core user has access to docker and systemd-journal.
The udev rules are required on our system and refer to non-existent
groups causing udev to spew a bit of useless noise on boot.
The profile.d scripts don't do anything at all.
docker has been known to crash from time to time in odd situations. Auto
restart docker 1 second after an unexpected exit so that people can go
about their business.
Thanks to dsal & fkautz in #coreos
Biggest diff here: coreos-init has a Makefile that supports the usual
'install' and 'test' targets so no file copying is required now.
coreos-c10n has moved to init from etcd and has its own service now.
This version of init also includes support for automounting virtfs
filesystems under qemu for use with an updated version of c10n but for
now c10n remains unchanged. Optionally unit tests are available too!
This adds the following patch: (sent upstream, waiting on response)
"9p: send uevent after adding/removing mount_tag attribute"
Also enable PCI hotplug to take advantage of more qemu fun! Now
adding/removing virtio devices (which are represented as PCI devices)
at runtime via the qemu monitor console works.
We don't have a valid kernel (or use-case to have one) for "cros_host"
(the SDK) so just fake it. Also remove some unused flags.
This change prevents the latest kmod ebuild from pulling in
coreos-kernel, bootengine, and friends into the SDK.
argparse is bundled into python-2.7 so dev-python/argparse cannot be
installed. Instead the virtual package should be used to work with any
python version combination.
They have some patches to fix cross-compiling in this build environment.
Start off simply by adding 2.7 as a new parallel install target, will
switch to 2.7 as the primary version in a later step.
This flag enables 'at_console' policy support using logind. I don't
think we actually have a use for that and having it disabled hasn't
caused anything weird that I know of so far so leave it disabled.
Enabling this flag causes a circular dependency between systemd and dbus
which is resolved in catalyst bootstrapped builds like the SDK but for
target builds this is a problem.
