I’m a little teapot 🫖

  • 4 Posts
  • 478 Comments
Joined 1 year ago
cake
Cake day: September 27th, 2023

help-circle







  • In my experience many of the people who haven’t quit are self medicating for attention or depressive reasons. Of the folks I know who vape about half were diagnosed with ADHD later in life (30+) and quit after finding a stimulant medication that worked for them. The rest are unmedicated and self medicating with nicotine and coffee or energy drinks. Self medicating is overlooked in virtually every discussion about nicotine and I’d like to see it considered more often when the topic comes up instead of just leaping straight to “nicotine use bad” or “nicotine users should be punished” like most discussions do.

    Edit: there’s also some interesting research re: nicotine’s neuroprotective properties that gets lost in the prohibition fervor




  • 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.







  • 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.



  • 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.