ElRenosaurusReg [fae/faer, comrade/them]

  • 0 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle










  • So, the big thing with instability is that with Linux “Unstable” refers to “Constantly receiving updates” rather than “Breaks all the time”

    In my experience, if arch breaks, 99% of the time YOU the user did it.

    If you want a kinkless experience with it, keep it simple.

    Arch ships with systemd, as such, it also ships with systemd-boot. Use what’s built, don’t add additional bootloaders unless you need the functionality they offer.

    Gnome, Matlab, and VScode have wiki pages for installation and configuration, and Firefox is in the repos and is one line in the terminal to install (#pacman -S firefox)

    For a first install, I’d recommend following the wiki to install instead of using archinstall to familiarize yourself with how to use and read the wiki.




  • For me, I’d edit things like timing as well as whether a given cylinder/rotor is actively firing based on engine load, disabling cylinders under low load (eg: already at speed, idling) to improve fuel efficiency and maximize power output for a given amount of fuel based on load and whatever the task at hand is (eg hauling loads, hauling ass, or gentle driving)

    Edited: I was really tired when I typed this and missed a couple very important words.



  • Suckless philosophy. The less computerization the better. I wanna be able to fix the whole thing with a 10mm, a jack, and an adjustable spanner.

    Currently I have a 92 Corolla, it has too many computerized parts and I’m planning to replace the engine with a carbureted 3 rotor and a manual transmission. Ideally, I’d also like to implement Koenigsegg freevalve as well.

    If all goes to plan, it could handle an EMP and keep running, though I’m not a prepper or anything, i just want a fully mechanical vehicle because I understand mechanics, but adding computers into the mix muddies the water.



  • Forced Snaps is a big one. If you’re not familiar, Snap is Canonical’s proprietary alternative to Appimage and Flatpak. While the Snap Store is open source and can be forked or modified as needed, the backend is completely closed source, which has vexed many members of the Open Source community.

    While the distribution itself is currently pretty solid, they’ve made questionable decisions in the past like including an amazon search function in their fork of gnome (Unity). Snap can be removed by a skilled user or someone well versed in search-fu, but their choice to have it installed by default, the be the default for package management, and to inject snaps in place of deb packages when installed via Apt, are all big red-flags given that nobody can see what is in those snaps til they’re installed except for canonical.