Can also endorse aptitude, but hopefully OP already has it installed prior to this issue. May have to manually install using dpkg if not. Whenever I run into issues like this, aptitude solves it 95% of the time, makes regular apt look like a baby helplessly crying.

Anyone else wanting to move to CoMaps but procrastinating because they’d have to go about downloading the maps again?

Wow! That’s much more that I would have thought. Can’t wait to liberate my dad’s phone over the holidays, he’s on board with me getting GrapheneOS on it. Will have to see what I can do to their home network as well though since mom’s stuck on a carrier-locked phone.

Minimal delay between a program releasing new features or bugfixes and you getting to use them. Even as an avid Debian user, sometimes I get bummed out when they freeze a package for release right before a feature I would have really liked makes it in.

As for security, there’s not a huge difference I’m aware of. On Debian, features stay where they are, but maintainers will backport just the security fixes of each package to the current stable release.

Me over here having to provide my own work phone because BYOD. At least it’s my old phone I upgraded from, so the cost is already sunk.

Saw the followup post, glad to hear its all running well. I created my VM using virt-manager with a raw disk image and UEFI firmware rather than the default qcow2 format with BIOS. I keep the image size down to 32 GB to save time when imaging. Install proceeds as usual, make sure fstab mounts disks by UUID, Debian does by default in my case. When everything is configured, dd the raw disk image over to the target disk, do the rituals to make it bootable, and consider configuring new partition UUIDs.

Linux: no, but not necessarily plug-and-play. My daily-driver install is literally pre-configured on a VM and cloned to all of my machines with various motherboards. Nvidia complications aside, a default Linux install will contain nearly every driver you could ever need to get up and running. However, some motherboards do need you to chroot from a live environment and make it “aware” of the existing GRUB bootloader.

Windows: At best, you’ll need to reactivate. More often, it’ll be missing a driver or just not work as well as it did on the old motherboard. It’s better to reinstall Windows.

Will admit that I’m very biased against reinstalling Linux anew except as a last resort since it’s a painstaking days-long process to configure things just right for my picky tastes.

If you have SMR drives, it is normal for them to rearrange their contents during periods of user inactivity. The way Shingled Magnetic Recording crams more bytes into the same platter necessitates its own kind of “defragmenting”. Unless it’s host-managed SMR, it’s done by the drive’s onboard controller, so the OS won’t be aware.

No, the more the merrier, even if it’s pure publicity.

Probably not without LVM or an external drive to restore from. Depending on which partition comes first, you’ll either have to extend the OS partition “leftward” or lop off the front of the data partition, and there isn’t a good way to do either nondestructively.

If you have LVM set up, you could reduce the storage partition, make a partition in the new free space, and lump it into the volume group for the OS partition.

Sorry about that, you are right. The way I originally envisioned would have disrupted the partitioning of the original ISO. Tried it myself and ran into the same issue, then finally recalled how I actually did it. See my edited comment above. Unfortunately, changing out the ISO non-destructively might be harder than I originally thought.

Looks amazing. I was just thinking about my friend who keeps Windows around for iTunes syncing yesterday, one more thing I can suggest to people moving to Linux.

The only time I find myself in line with CLI purists is when I need to SSH into a machine without X forwarding. Had no idea that there were terminal PDF viewers, but now I know if I ever need to consult a document remotely.

My friend

• loves making and sharing home videos, but his entire workflow is tied to Windows Movie Maker
• his wife insists on using an iPhone and is tech-illiterate, so depends on him having iTunes for syncing stuff
• has bad memories of Linux from the 2000s and has grown comfortable with a copy of Windows that I’ve debloated

If you don’t want Ventoy:

1. Wipe the USB: wipefs -a /dev/sdb
2. Copy the ISO image to the USB: dd of=/dev/sdb if=/path/to/image/linux.ISO bs=1M status=progress
3. Make the data partition in the free space: cfdisk /dev/sdb, don’t remove the iso9660 signature, create partition in the free space, and Write.
4. Format the partition with filesystem of your choice: mkfs, cryptsetup, etc.

(everything as root, replace /dev/sdb with the location of your USB)

As is, this only leaves exactly enough for the ISO you are currently working with, sealing the fate of the data partition if you need to swap out the ISO. I suspect there is a workaround in theory, but I haven’t gotten around to that yet.

Also see https://github.com/thias/glim, a GRUB-based alternative to Ventoy, albeit with less compatibility.

Edit: this will not work with Windows ISOs and the data partition won’t show up in certain versions of Windows, in case anyone is wondering

You’ve survived and perhaps thrived booting off the HDD for a while, so I would wipe the SSD and install Linux there if you intend to switch over at some point. That’s what I did for my test bench, my last personal machine with Windows; Linux on an SSD and Windows on an old HDD, where the slow speeds don’t really bother my infrequent use.

As someone who did use this guide as an exercise in making my setup as secure as it could be without changing distros or hampering productivity, a few words of advice:

• Make a threat model for yourself before diving in and apply the mitigations judiciously. It’s not exactly a checklist, just use something secureblue or Qubes if you are really paranoid about your computer.
• The majority of the mitigations ‘just work’ and have no noticeable impact on performance, battery life, or compatibility.
• If your CPU/Memory performance widget breaks, dial back on the ptrace options
• If Flatpaks fail to launch, dial back on the namespace options
• Check back every so often because some of the options end up having unwanted side-effects with updates. See the preamble in boot parameters, where a change in Linux made in 2021 (which finally made it into Debian Stable this year) made the slub_debug mitigation actually worsen security.

Even if they did, your messages are going to be scanned via your recipients who use Gmail without opting out.

Interesting, had no idea until now that there’s such a thing as first-party malware loaded with the BIOS. Admittedly I’m caught in an ivory tower with my Corebooted ThinkPad. Although I haven’t purchased one yet, I’d say you made the right choice going with Framework.

Lenovo’s ThinkPad line has a sterling reputation. Among the best in terms of quality, service, repairability, and Linux support.

As for the largely consumer-grade options of ASUS and Lenovo’s consumer-grade IdeaPads, they’re rather similar in reputation and quality. Not exceptional, but they’re both perfectly fine options as long as you avoid the budget laptop segment (plastic chassis, broken hinges, etc.)

Any difference in privacy would come down to the pre-installed software, which is irrelevant if you plan on using Linux. If you will be using Windows, it’s always better to install your own fresh copy to purge any potential spyware and bloatware installed by the manufacturer. The activation key for whichever edition of Windows it comes with is embedded in the BIOS, so it’ll activate automatically after a fresh reinstall.