don't want installed by default. Some are tools that aren't needed for
non-interactive use; some are libraries whose reverse-dependencies
will have already been removed; and one, open-vm-tools, should only be
included in images that are targeted to VMWare (which is not the case
for any of the current minimal images), rather than being included
directly in the cloud-image seed.
Kernels which are able to boot without initramfs now dropped dependency
on initramfs-tools thus initramfs-tools can be removed from the image
instead of having to divert it to avoid initramfs generation.
- Usually, netplan's systemd-generator enables systemd-networkd and
systemd-networkd-wait-online on boot. But netplan configuration is not
yet generated at that point by cloud-init. Cloud-init generates in the
network-pre.target and expects the network.target /
network-online.target to work. These are already part of the ongoing
systemd transaction, thus cannot be injected into the boot-sequency by
cloud-init local mode. Therefore make sure cloud images include
networkd in the initial boot transaction.
- src:systemd will shortly not enable networkd unconditionally by
default.
* Drop ifupdown e-n-i configuration files, no longer used.
* live-build/ubuntu-cpc/functions: Add a function, teardown_mountpoint,
to reverse the work done in setup_mountpoint. Lack of this function
has forced users of setup_mountpoint to implement this separately
and the implementations have diverged. (LP: #1716992)
* live-build/ubuntu-cpc/functions: Remove umount_settle function.
The was only used where teardown_mountpoint was lacking.
we don't have to leave empty space in our derivative images for packages
that have been downloaded/installed/removed. This normally isn't
relevant for the installed system, since the root filesystem will
auto-expand in place on the target disk, but lets us ship smaller
images.
* live-build/functions: also call 'apt-get update' after mounting the
blank /var/lib/apt.
This branch changes the behavior for default users on the vagrant image,
according to much of https://www.vagrantup.com/docs/boxes/base.html
Specifically, this adds a new "vagrant" user with a know password on top
of the already existing ubuntu user.
This conforms to the expectations of the Vagrant community, despite some
security concerns. Vagrant images are not used for production systems but
for development environments, and the absence of the "standard" vagrant user
has been hurting ubuntu adoption on that platform.
