On Wed, 2017-09-27 at 09:21 +1000, Julian 1 wrote: > I am affected by this as well. > > Googling shows shows people experimenting with workarounds - creating an > additional unencrypted /boot partition independent of the unencrypted EFI > partition. > > This is overly complicated when the subsequent install workflow already > does the correct thing - in creating a /boot partition and > kernel/initrd/grub on the EFI parition. > > One just needs to be able to hint that the EFI/fat32 parition will be used > for /boot, or else simply let the user 'continue' the installation, rather > than have both 'go-back' and 'continue' return to the same menu. [...] DO NOT use a fat32 partition for /boot! It will appear to work, but the first upgrade of a package that installs into /boot will fail because dpkg cannot create a hard link there. Ben. -- Ben Hutchings Larkinson's Law: All laws are basically false.
Attachment:
signature.asc
Description: This is a digitally signed message part