only use a partition from the blockdev holding the livefs for auto logs
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1926137 describes
a situation where a partition called "writable" on the disk the user
wanted to install to was mounted and then caused the install to fail.
To avoid this, change things to only write logs to a partition on the
same block device as that holding the livefs by default.
New changelog entries:
* Move check for fallback persistent filesystem label (casper-rw) later as
it seems sometimes it takes time for block devices to appear and be
processed by udev. (LP: #1863672)
New changelog entries:
* Make fsckd under spinner/logo themes produce consistent output
* Make plymouth-less progress output less bad
* Use theme-specific keys: or fsckd-cancel-msg: for Ctrl+C message LP:
#1870018
* Add fsck.mode=skip sensitivity to casper-md5check
* ubuntu-server: skip mounting swap (as hacked by livecd-rootfs currently)
* Leave fsck result as a json /run/casper-md5check.json file.
* ubuntu-server: adapt runtime netplan into cloud-config cloud.cfg
* Fix cmdline parsing, it was always broken
New changelog entries:
* casper-md5check:
+ flush pending events for actually fluid progress updates
+ drop reboot includes
+ watch for s keystroke to skip checks
+ always finish on 100% update, to remove the progress message
+ always drop the keystrokes message
+ always display the result of the checks, with a slight delay
+ make the failed message linger for longer
+ clear all messages before quiting
+ ignore unused-result warnings during compilation
New changelog entries:
* casper-md5check:
+ Use fsck progress text, whilst verifying the disk.
+ Do not reboot, but simply continue booting after the integrity check.
+ Perform integrity check on every boot (TODO allow skipping the check)
New changelog entries:
* Create partitions with label "writable" rather than "casper-rw" (but still
use a partition with label "casper-rw" in preference to creating one).
(LP: #1861512)
