losttourist

Linux doesn’t really know about drives, it knows about partitions and mount points.

Obviously this is a simplification, but in general it’s close enough. It also could well be your problem - timeshift doesn’t know or care that /boot is on the same physical drive as the rest of your system: if it’s a different partition, it’s separate.

Not really a viable solution for many scenarios though. What if your PDF has half a dozen pages, your answer becomes really tedious. And in a lot of cases a PDF with forms is expected to be sent back to the person or company that created it once the fields have been filled in. They’re not likely to want to receive a bunch of JPEG screenshots instead.

From the sidebar

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.

Nothing there saying it’s specifically for Linux News.

That all seems … incredibly complicated.

Why not use fwupd? (link is the Arch wiki but should be relevant for any distro). I’ve been using fwupd to keep my Dell XPS15 BIOS updated for the last few years, with no problems at all.

I’m still struggling to understand what advantage Docker brings to the set-up.

Maybe the application doesn’t need to write anything to disk at all (which seems unlikely) but if so, then you’re not saving any disk-write cycles by using docker.

Or maybe you want it only to write to filesystems mounted from longer-life storage e.g. magnetic disk and mark the SD card filesystems as --read-only. In which case you could mount those filesystems directly in the host OS (indeed you have to do this to make them visible to docker) and configure the app to use those directly, no need for docker.

Docker has many great features, but at the end of the day it’s just software - it can’t magic away some of the foundational limitiations of system architecture.

I’m not sure why Docker would be a particularly good (or particularly bad) fit for the scenario you’re referring to.

If you’re suggesting that Docker could make it easy to transfer a system onto a new SD card if one fails, then yes that’s true … to a degree. You’d still need to have taken a backup of the system BEFORE the card failed, and if you’re making regular backups then to be honest it will make little difference if you’ve containerised the system or not, you’ll still need to restore it onto a new SD card / clean OS. That might be a simpler process with a Docker app but it very much depends on which app and how it’s been set up.

Do you want zombie orphans? Cos that’s how you get zombie orphans. Listen to the AI, it’s trying to save the world from becoming a dystopian TV series!

Neither sausage-on-a-stick fast food nor sausage-in-a-bun fast food bear any resemblance to the traditional German way of serving wurst. Neither is “closer” they are both a million miles away from the original.

While true, I think most people’s concern is that their laptop is stolen and along with it all the access details for their email, online banking and so on.

If you’re doing things that mean you’re going to be the target of people with the knowledge, time, and technology to freeze the RAM and attempt to recover the data, you’re presumably already well aware of those (and other) dangers anyway.

GRUB (or any other bootloader) doesn’t care about and in fact doesn’t even know about X, Wayland, or any other userland GUI system.

CPU requirements for Lemmy hosting are minimal. Memory is useful - you’d want to use the Pi 4 with either the 4GB or 8GB RAM, anything less than that will work but you’ll be running the risk of difficulties if the server gets busy.

You’ll also need plenty of storage, especially if people are going to start uploading media to your Lemmy host. Given that a Pi runs off an SD card you might well find yourself running out of storage space - I’d recommend attaching a USB storage device for the reassurance in that respect.