With systemd v233, the units linked in default.target.wants are not
started. This enables the config targets as multi-user.target
dependencies instead.
Ignition (starting with 0.14.0) will apply this configuration
instead. This also depends on coreos-metadata supporting
PACKET_PHONE_HOME_URL, which will be present starting in 0.8.0.
We've always generated these license manifests (detailing which ebuilds
are covered by which license), but never published them. This adds these
manifests to the list of published files so that they are publicly
available.
os-release is requested in bug reports, and knowing which board
the problem occurred on is often helpful.
Signed-off-by: Geoff Levand <geoff@infradead.org>
There is no need to fork the daemon with systemd, so run in the
foreground for Type=simple. This also writes logs to stderr by
default, so this service no longer needs a special /var/log path.
The syslog.target unit does not exist either, but SSSD can
can optionally query NSCD, so order it after nscd.service.
There is a dependency loop when systemd is build with cryptsetup
like systemd -> cryptsetup -> lvm2 -> baselayout -> systemd. Since
CoreOS always installs a good baselayout, it makes sense drop the
lvm2 dependency and turn it into a conflict with bad versions. It
also has a runtime dependency loop on systemd, so make that into a
build dependency.
This also stabilizes the version that was being used by arm64,
updating amd64, to bring the architectures into alignment.
Changes include:
* Add cros_workon bits
* Define and use the symlink-usr flag
* Drop SELinux policy and udev init scripts dependencies
* Drop all patches since the source is from Git
* Switch /etc/resolv.conf to the old one
* Drop the D-Bus policy path to keep the default
* Use CoreOS NTP servers
* Install PAM files into /usr
* Set the timesyncd epoch
* Don't use default DNS servers
* Use legacy cgroups (https://github.com/docker/docker/issues/28109)
* Rewrite basically the entire install step
* Drop the systemd-bus-proxy user since the program is long gone
The actual nscd binary has been installed since sssd was added,
but none of the systemd configuration files were included. This
resulted in a binary that would not start due to a missing /run
directory.
The upstream nscd.conf is installed in /usr and linked into /etc.
