![](https://media.kbin.social/media/6b/b0/6bb0e11b68593c16221270787d5117ad012ff721608633ee70d14c10d56326bc.jpg)
![](https://lemmy.ml/pictrs/image/st9xYggWap.png)
Without a published POC there’s a slightly longer window before clueless script kiddies start having a go at exploiting the vulnerability, though.
Modern tech, retro tech, 80s/90s music & nostalgia. I live in northern England so most things I post about have a UK slant.
Elsewhere on Fedi:
Without a published POC there’s a slightly longer window before clueless script kiddies start having a go at exploiting the vulnerability, though.
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.
You might enjoy Peter F Hamilton’s books Pandora’s Star and its sequel, Judas Unchained. It’s somewhere between space opera and hard sci-fi but there are significant plots and sub-plots involving alien creatures ranging from the vaguely comprehensible (to humans) through to creatures that are almost beyond our ability to understand.
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!
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.
Answering my own question - I actually needed to search for @manchester@mcr.town and now I’m subscribed. Well done the Fediverse.
@Otome-chan@kbin.social Was that the person who posted saying “I wrote something on Kbin and somebody replied to me from Mastodon and OMG what are they doing sending my stuff everywhere?”
I know that it can be hard to grok the Fediverse when you first stumble across it, but there have been no shortage of attempts to explain it in the last few days.
You may have slightly misunderstood the Fediverse.
Accounts are not shared between different systems. They’re not even shared between different instances of the same system.
What gets shared is the content, and the knowledge about other accounts.
So you can follow a Kbin user from Mastodon, or vice versa. A Mastodon user can boost (“retweet”) something posted by a Lemmy user, on Lemmy. A Kbin user can upvote (“favourite”) a post that’s on Mastodon. A Calckey user can reply to a Kbin post, and that reply appears on Kbin and Mastodon and everywhere else that the thread is visible. And so on.
But your actual account, i.e. your username & password and the profile associated with it, are firmly and permanently associated with the specific server you initially registered with.
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.
Apple in the 21st century are exactly like Microsoft in the 20th: they view open source and public protocols as an active threat to their business model and will go miles out of their way to ignore any FOSS project even if it could be hugely beneficial to them.
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.