this post was submitted on 09 Jun 2024
733 points (98.5% liked)

linuxmemes

21222 readers
85 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     

    It’s not really broken, couldn’t get the microphone to work with any program

    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 18 points 5 months ago* (last edited 5 months ago) (1 children)

    Second approach is better as it teaches you to fix and understand the system you're working with

    Of course, this is a more complicated and energy - demanding approach, though. But if you wanna stay on Linux, you better figure such stuff out, this will be invaluable in the long run.

    I should also mention that Debian, despite the Bookworm introducing more user-friendly options, is not a newbie-centered distribution and fixing things in there tend to be more tedious for an inexperienced user.

    The upside, however, is that once you've set it up, everything will just work. But first you might face some pain.

    [–] [email protected] 6 points 5 months ago (4 children)

    I wish there was a way to see what the default values in a config file are for a given distro.
    I'm guessing there probably is, and I just don't know it.

    Maybe I should just make / a git repo...

    [–] [email protected] 2 points 5 months ago

    Without knowing a better way, my go-to solution woukd just be getting an full installation image and diffing my files with the files on it

    [–] [email protected] 2 points 5 months ago

    Don't modify the config in /etc/, copy them in ~/.config/ and then modify them. You'll always be able to just look at the /etc/ for defaults.

    [–] [email protected] 1 points 5 months ago* (last edited 5 months ago)

    Usually if its a boolean or nullable, a good config file will have a # uncommemt this line to enable this feature/disable this feature/bind to this IP address/give this thing a name that is at least vaugely hints what the option does. But yes, its still fairly annoying.

    [–] [email protected] 0 points 5 months ago

    You should check out the Fedora atomic distros if you haven't already. Making the system work more like a git repo is what they are doing with rpm-ostree. I am liking it a lot.