There were shadowy conspiracists lurking in the dark alleys of Washington, and hiding from the glaring sun in the High Desert of California, but they were laughably easy prey when the Martian lizard people, the subterranean Vril-empowered mole-men, and the globalist pedophile Commies did show up.

  • 34 Posts
  • 1.94K Comments
Joined 9 months ago
cake
Cake day: July 15th, 2024

help-circle



  • What makes an Arch system an Arch system is the repos, the package manager and the fact that you installed it yourself.
    Anyone giving you support will expect you to be able to answer a couple of questions about your system based on the fact you yourself configured it.
    With EndeavourOS, even if you have the exact same repos, it still wouldn’t be an Arch system.
    And now get off my lawn!





  • I eventually gave up trying to make myself exercise every day.
    But I am fortunate enough that I could chose to live within cycling distance of my work.
    Now I bike to work every day, which is technically transportation, not exercise, so I don’t mind it.
    This summer I’m going to move into an apartment 11 miles from work. I’m really looking forward to it.





  • I tried Silverblue.
    And I wanted to run it without layering, cause everyone tells you to avoid it, since it kinda defeats the purpose of an atomic distro in the first place.

    First of all, it was buggy. As an example, automatic updates didn’t work, I had to click the update button and reboot twice for it to actually apply, even though it was activated in the settings.
    None of the docs helped (actually, there wasn’t any in-depth documentation at all). And no one had a solution besides “It should actually just work”.
    That’s the main advantage (the devs test with the exact same system you run) gone right from the start.

    Then Firefox is part of the base image, but it’s Fedora’s version, which doesn’t come with all codecs.
    If you install Firefox from Flathub, you now have 2 Firefox’s installed, with identical icons in the GUI. So you need to hide one by deleting its desktop file. Except you can’t. So you have to copy it into your home directory and edit it with a text editor to hide the icon.
    Then I went through all the installed programs to replace the Fedora version with the Flathub version, cause what’s the point of Flatpak if I’m using derivative versions? I want what the app’s dev made.

    Then it was missing command line tools I’m used to. Installing them in a container didn’t work well cause they need access to the entire system.

    Finally, I realized even Gnome Tweaks wasn’t part of the installation, and it isn’t available as Flatpak.
    That’s the point where I tipped my hat and went back to Debian. Which isn’t atomic, but never gave me any issues in the first place.

    Maybe it’s better now, I was on the previous version. Or maybe the Ublue flavours are better. But I don’t see any reason to start distro-hopping again after that first experience.


  • What I did was [add Flathub, don’t remember if it’s already done by default, and] go through all installed apps in the software center once, check if the Flathub version was made by the app’s devs directly, and if so, switch the source from Fedora to Flathub. I only kept the Fedora version if the Flatpak was made by an independent third party.

    I’m not sure if Silverblue is even the right distro for me if I care about such things this much, though.






  • Powershell supposedly is really great once you’ve understood how it’s structured.
    I keep hearing it’s more logical and discoverable than Bash.
    Maybe that’s true, I keep bouncing off it and getting frustrated. And when I try to read up on it, the explanations throw low level programming terms at me, which I’m too stupid to understand.

    But modern Windows has one thing going for it, which makes it similar to Linux in concept:
    Literally everything can be done with Powershell, and literally every config can be manipulated manually when you know where to look.

    Configs are a bit strewn around the system, though. They can be in your user folder in AppData, or globally in C:\ProgramData or only in the Registry.
    And some software says “Fuck all this” and puts them in C:\Program Files, C:\Program Files (x86) or even in an own directory on C:\ But that’s no different on Linux, really.

    Then you can look at group policies, which are like an extended settings menu for thousands of things that aren’t in the GUI.
    And since you can write your own group policies that set arbitrary Registry values, you can make Windows your bitch.

    The main issue really is documentation. It either doesn’t exist, or it’s wrong, or only available to Microsoft employees.
    So even if you have 10 years of experience in administering Windows systems, you’re still hunting through forums for answers.

    The most important resource an experienced Windows admin can have is a list of bookmarks to trustworthy sysadmin blogs.

    So, to recap: Windows is the Registry. If it reads a config file from somewhere, the path to that config file will be in the Registry. If you change a setting in the GUI, via Powershell, or a group policy, the setting will be saved in a Registry key. Unfortunately, many Registry keys are not legible by humans. And Regedit as a tool absolutely sucks.