Comment 3 for bug 1767896

It is a nice machine :) This one was signed by David Hill, so it's a real treasure :)

I can try to dig up the info you requested, but first I have to state that I don't even know what snapd is :( I can say that "apt purge snapd ubuntu-core-launcher squashfs-tools" made it stop eating my CPU.

It's an easy thing to set up, but might require a 2nd drive. Primary drive in an NVMe SSD with Lenovo's Win 10 preload on it. Secondary drive is a SATA SSD in the WWAN slot. One FAT32 partition, one NTFS.

I put Ubuntu as a live "install" in the FAT32 partition for a couple of reasons - which may be off-base. 1st, it's intended as backup/fallback/recovery tool if the primary drive fails. Since an _installed_ Ubuntu wants to add its boot stuff to the EFI partition on the primary, that wouldn't be much of a fall-back if primary fails. The live install can boot directly from the T's boot menu w/out needing the primary drive. The other reason is that when it's in a FAT32 partition it can be manipulated from Windows and v/v without having to add any additional fs tools, and no additional partitions are required. I also use the grub in the FAT32 partition to boot things like memtest, Acronis, and some other stuff. It ends up looking like one of my "Swill-army" flash drives. Backup is also facilitated.

Back to how to set up: I just copy the contents of the Ubuntu ISO to the FAT32 partition. Then create a persistence file and edit grub.conf to allow the option of persistence or not. I've got an old writeup on how I make my flash drives. The process is the same, but _installing_ grub isn't required since it's a UEFI-only setup:

http://www.beezmo.com/geezblog/?p=428

I'm happy to dig for details if that will help - but will probably need some guidance.

Thanks!