I’m a little teapot 🫖

  • 1 Post
  • 46 Comments
Joined 10 months ago
cake
Cake day: September 27th, 2023

help-circle

  • For data like this from another filesystem I usually like to mount the entire volume somewhere private (like under /run) and then bind mount the parts I want to use into their desired locations (like /home/foo/Download, etc.)

    I do this with a second ext4 drive that I use for performance sensitive storage with my primary btrfs system root. It works well, just be aware of edge cases involving containers (you may have to grant the container access to the original mount location under /run in addition to the bound path. This is definitely a gotcha when working with those paths with flatpak.)











  • I’m onboard with 65 as the maximum age anyone can run for Congress but I don’t have a problem with people 65+ finishing their terms provided they’re actually competent. I’d like to see mandatory cognitive decline testing for anyone running for Congress, appointed to the SC or appointed to any high position in the executive branch.

    It’s absolutely ridiculous that we’re allowing people with 5-7y remaining life expectancy to plan our future 20, 40 or 100y out - they just don’t have the skin in the game that someone in their 20s or 30s does.

    On top of all of that I’d like to see vigorous corruption testing, SC justices and congresscreatures shouldn’t be bought and paid for the way they are now.




  • They’re also completely missing the point of distro kernel trees. Stable automatically selects patches from mainline (largely by keyword, and often without kernel developer feedback or involvement) and consequently has a massive amount of code churn and very little validation beyond shipping releases and waiting for regression reports. Distro trees are the buffer where actual testing happens before release. As a long term stable user it really isn’t suitable for end user or enterprise consumption unless you have your own in house validation process to test releases for regressions before deployment. Even running stable on client machines (desktops, laptops) leads to a bad time every few weeks when something sneaks in that breaks functionality.