I didn’t

It’s also likely that the mSATA slot is bottlenecked since it runs at SATA II speeds while the 2.5 bay runs at SATA III speeds. This becomes noticeable with heavy swapping or flatpak updates. I found this out the hard way because I want my boot drive on my 256 GB mSATA instead of the 2 TB SSD that I use for media and backups.

I’m also considering this when it comes time for me to update. I would:

• Throw a spare SSD or equal or greater size into a USB enclosure
• Clone my boot drive to it using Clonezilla
• Remove the original boot drive to avoid UUID collisions
• Boot off the spare SSD and perform the update

When maximizing uptime, Debian is the no-fuss way to go.

Well said. LUKS implements AES-256, which is also entrusted by the U.S. government and various other governments to protect data from state and non-state adversaries.

Possibly overestimating the value of the data entrusted to me, but whenever I see that xkcd, I like to think that I at least have the option to remain silent and die with dignity if I really don’t want the contents of my disk out there.

I wish I found a guide like that back when I first made the move to FDE. Regardless, I was adamantly against reinstalling and painstakingly replicating my customizations, so I came up with a hacky way of tacking on FDE.

It went something along the lines of:

1. Shrinking the root partition as much as possible
2. From Live CD, dd root partition to external drive
3. Perform minimal encrypted install of Debian
4. From Live CD, open LUKS container of the newly-installed Debian and overwrite the root partition within with my old root partition.
5. Update fstab, crypttab, initramfs, and grub
6. Cross my fingers and reboot

The text editor shortcut on my taskbar runs a sort of autosave script in ~/.drafts. I wanted my text editor to function more like the one on my phone so I can just jot down random thoughts without going through the whole ritual of naming and saving. It creates YYYYMMDD_text in ~/.drafts (or YYYYMMDD_text_1 etc. if it already exists) and launches Pluma, which I also have configured to autosave every 10 minutes.

The other thing extends beyond Linux itself a bit. I like to joke that I have the most secure NT 4 / Windows 95 lookalike ever put together. Aside from the encrypted and hardened Debian base (/boot is also encrypted), I was in part inspired by Apple’s parts pairing (yikes!). So my coreboot is configured to only accept my boot disk. If it’s swapped out or missing, or if I want to boot something else, it will ask for a password. In the unlikely event my machine gets stolen, the thief must at a minimum reflash the BIOS or replace the motherboard to make it useful again. Idk, it amuses me every time I think about it.

It’s nice getting a glimpse as to what fraction of Linux users are using disk encryption. Full disk encryption is becoming the default on mainstream OSes, but not in most of the Linux installers I’ve encountered. Always made me curious just how many people went out of their way to encrypt their Linux install.

I personally encrypt everything except for VMs already in an encrypted device or USB drives that need to work with non-Linux machines. It’d be interesting to hear what other people’s reasons to encrypt their disks or not are.

Biolinum O for desktop

Liberation Mono for terminal

I’ve used this Windows 10 live image to run the occasional windows-only diagnostic tools and firmware updates: https://github.com/VulpesSARL/MiniNT5-Tools

It doesn’t choke loading GUI programs like the install disc command prompt and doesn’t have any weird blobs except for windows itself.

The level of detail and control in the Properties dialog from the file explorer in Windows. Also its ability to easily search by metadata like the bitrate of media files.

Ideally, 256 GB + microSD. 128 GB today gives me ample room for my offline maps, music collection, podcasts, and Kiwix libraries. No gaming, only the occasional video, and one photo per day on average, so 256 GB would future-proof it.

As for a minimum, 32GB. For several years, I had a phone with 4GB of internal storage. Didn’t use the microSD slot since it seemed to drain the battery. Android takes up much more space nowadays, but I wouldn’t be too upset having ~16 GB usable space for myself.

The SD card would be separately encrypted as a portable backup of everything important to me, accessible on-the-spot whenever I need it.