empty-fstab-in-lxd : lp:~rbalint/livecd-rootfs : Git : Code : livecd-rootfs

Get this branch:: git clone -b empty-fstab-in-lxd https://git.launchpad.net/~rbalint/livecd-rootfs

Only Balint Reczey can upload to this branch. If you are Balint Reczey please log in for upload directions.

Branch merges

Merged into livecd-rootfs:ubuntu/master at revision 90602e00de30617e744f904dbb38c2e07360c536

Dimitri John Ledkov: Approve on 2020-06-23

Ubuntu Core Development Team: Pending requested 2020-06-16

Branch information

Name:: empty-fstab-in-lxd

Repository:: lp:~rbalint/livecd-rootfs

Recent commits

f96e874... by Balint Reczey on 2020-05-25

Remove fstab from squashfs images

The default fstab is not valid, since squashfs does not support labels.

LP: #1877078

4010343... by Łukasz Zemczak on 2020-05-25

Enable overrides of UC20 grade dangerous channels

60665a4... by Philip Roche on 2020-05-18

Revert of initramfs package removal in KVM image (LP: #1875400)

It was reported and confirmed in LP bug #1875400
(https://bugs.launchpad.net/cloud-images/+bug/1875400) that on the public
KVM cloud image there exists a large list of packages marked for auto-removal.

This should never be the case on a released cloud image.

These packages are marked for auto-removal because in the KVM image binary hook
we removed both initramfs-tools and busybox-initramfs packages. Due to package
dependencies this also removed:

busybox-initramfs* cloud-initramfs-copymods* cloud-initramfs-dyn-netconf*
cryptsetup-initramfs* initramfs-tools* initramfs-tools-core* multipath-tools*
overlayroot* sg3-utils-udev* ubuntu-server*

But it did not remove all the packages that the above list depended on.
This resulted in all those packages being marked for auto-removal because they
were not manually installed nor did they have any manually installed packages
that depended on them.

The removal of initramfs-tools and busybox-initramfs was to avoid the
generation of initramfs in images that should boot initramfsless.

This requirement is obsolete now because the initramfsless boot handling
is now handled via setting GRUB_FORCE_PARTUUID in /etc/default/grub.d/40-force-partuuid.cfg.

In test images I have verified that GRUB_FORCE_PARTUUID is set and that
boot speeds have not regressed.

LP: #1875400

9640e60... by Dimitri John Ledkov on 2020-05-12