I mean, given how many people live we already kinda do
I’m a little teapot 🫖
I mean, given how many people live we already kinda do
That’s maybe not the best approach to take unless you’re wealthy enough to hop on your jet and fuck off somewhere stable while it happens. Things are going to get ugly when people can’t get their medication, food, energy to heat their homes, etc.
Don’t just look at sdb hits in the log. Open up that entire session in journalctl kernel mode (journalctl -k -bN
where N is the session number in session history) and find the context surrounding the drive dropping and reconnecting.
You’ll probably find that something caused a USB bus reset or a similar event before the drive dropped and reconnected. if you find nothing like that try switching power supplies for the HDD and/or switching USB ports until you can move the drive to a different USB root port. Use lsusb -t
and swap ports until the drive is attached beneath a different root port. You might have a neighboring USB device attached to the bus that’s causing issues for other devices attached to the same root port (it happens, USB devices or drivers sometimes behave badly.)
Always look at the context of the event when you’re troubleshooting a failure like this, don’t just drill down on the device messages. Most of the time the real cause of the issue preceded the symptom by a bit of time.
This is just the first convenient target for libs to vent their frustration on. We’ll see a few more before the self flagellation resumes in earnest.
Ah, here we go, we found a minority group to blame for the election outcome in 3 days. Anyone want to place bets on the next group?
They’ve done it more than once now
Whatever they can get their hands on, including your unique hardware identifiers
Friends don’t let friends use Manjaro
They’ll find some way to make this change break the AUR again
I’m fine with posts about leopard cannibalism 🍿
Write a couple of your own toy services as practice. Write a one-shot that fires at a particular time during boot, a normal service that would run a daemon and a mount service that fires after its dependencies are loaded (like, say, a bind mount that sets up a directory under /run/foo after the backing filesystem is mounted - I do this to make fast ext4 storage available in some parts of the VFS tree while using a btrfs filesystem for everything else.) You can also write file watcher services that fire after changes to a file or directory, I use one of those to mirror /boot/ to /.boot/ on another filesystem so it’s captured by my system snapshots.
I’d start by reading the docs so you have some ideas about what services can do, then you’ll find uses that you wouldn’t have thought of before.
The wrong Amazon is burning
Nothing says love like bringing a noose
I’m anticipating the biggest and best hit of schadenfreude ever as we watch these clowns get the same treatment leftist activists have been receiving since the 1950s. Hell, we got beaten with clubs and shot with rubber coated bullets just protesting the Gulf war or income inequality. Let the folks trying a coup get a taste as well.
+1, I used EndeavourOS
I had to set one of these up for my SO a couple of years ago. I dropped EndeavourOS on it, installed btrbk and configured automatic snapshots on a schedule and before package installation/update in case she managed to bork things by pip installing things into system python.
Fedora would probably work well too if you want a lower maintenance burden. I hesitate to suggest Ubuntu or Debian or their derivatives since you’ll probably want to be somewhat current with your Nvidia drivers.
I wrote simple hooks for my package manager to fire system snapshots before I install or update any package. It’s a nice safety belt that I’ve never actually needed to use, but if I do need it it’s there.
I wouldn’t bother with the cdr or dvdr either, they’re likely to be dead too in 30y.
They’ll turn him into an animatronic corpse before they let him die in office