200% markup doesn’t matter when you’re billing it straight to the client anyway 🍻
I’m a little teapot 🫖
200% markup doesn’t matter when you’re billing it straight to the client anyway 🍻
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
Emacs users be like
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.
+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.
We usually find solutions or workarounds to Nvidia driver issues within a day or two in the Arch community. The absolute worst case handling I’ve had to do was fork the Nvidia dkms package at the prior version (think nvidia-dkms-550
) and run that until Nvidia themselves released a fixed version. Still pretty straightforward.
The most helpful advice I can give to anyone running a distro maintained by folks with day jobs is “take system snapshots before updates” - do that and the worst case fix to any update problem like this is still really easy to handle, even if you’re 10 minutes out from a work call and an update just went wrong.
I take daily work log notes in obsidian, then transclude chunks from those notes into topic notes and attach config files, images, context from the web, etc.
That matches with our experience from the US to the EU. Long haul is about 50/50 IIRC, you have to hunt a little bit to be sure the flights you book are Airbus
You have to check each flight for long haul. My SO did a round trip from the US west coast to Germany recently for work and something like 2/3 of the Lufthansa flights were Airbus, the rest were Boeing
I stood ready to pay and then the cashier said “now I just need your phone number and you can pay”. Hold up. What. I did not expect that, I honestly had a burst of anger inside me (never gonna take it on a cashier, they are just doing their job). I asked nicely why do I need to give my phone number and I was told that to register me as a member so I can get the discount.
“Sure thing, It’s +XX 111 222 3333” Just give them garbage.
Usually European companies prefer Airbus. Lufthansa is usually a safe bet.
US companies? Best of luck.
Please drink verification can
Compliance with sanctions from the US and EU IIRC
I moved my elderly mother to ChromeOS and I no longer have to deal with the IT burden of supporting whatever she installed or broke this week. Move your parents to Linux if you truly enjoy being an on call unpaid helpdesk
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.