getty: autologin as root on serial consoles
core: enable more cgroups by default
journald: limit RuntimeMaxUse to 4M
fstab-generator: When parsing the root= cmdline option, set FsckPassNo to 1

[tomegun: without this we would never fsck the rootfs if it was directly
mounted 'rw' from the initrd. We now risk fsck'ing it twice in the case it
is mounted 'ro', so that should be addressed in a separate patch.]
units: make fsck units remain after exit

Without this, fsck would be re-run if any other service which pulls
in a target requiring one of the mounts was started after fsck was done
but before the initial transaction was done.

https://bugs.freedesktop.org/show_bug.cgi?id=66784
fsck: disable emergency mode on failure

If fsck detects a big problem it might exit with a code that causes
the system to abort boot and enter dracut's emergency shell.

That is probably not the experience we want for the user at this time.
Continue booting beyond fatal errors, as we would have done before
fsck was running.
fsck: disable root fs check

systemd-fsck-root is only really useful for setups unlike ours where
the initramfs doesn't do the fsck of /.

More recent systemd versions only enable this service when /etc/fstab
asks for it (ours doesn't). Remove the auto-enable of this service to
match that desired behaviour.
fstab: always mount sysroot rw

EOS-2.1.0 shipped with /sysroot mounted here as read-only, and "ro" in
the kernel boot args, and a static /etc/machine-id in ostree for all
installations.

To correct the machine-id situation, machine-id has been removed from
ostree. So when upgrading from EOS-2.1.0, /sysroot must be mounted rw
so that machine-id can be generated early during first boot into the
upgraded OS.

We don't have any mechanism to fix up the boot args during the upgrade;
we can't fix this in ostree because the upgrade is driven by the ostree
version already shipped in EOS-2.1.0.

Instead, this change makes the ro/rw parameters be ignored at the
initramfs
level, now we always mount sysroot rw.

https://github.com/endlessm/eos-shell/issues/3171
hostnamed: prefer DMI information to ACPI for chassis type

At least for the devices we care about, this seems to be more
reliable...