this post was submitted on 10 Feb 2025
1 points (100.0% liked)

linuxmemes

23519 readers
2233 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 users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • 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.
  • 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, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. 🇬🇧 Language/язык/Sprache
  • This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
     

    Let the apologists have a field day in the comments.

    top 11 comments
    sorted by: hot top controversial new old
    [–] lka1988@lemmy.dbzer0.com 0 points 1 month ago* (last edited 1 month ago) (1 children)

    I don't care if settings are done by GUI or terminal, I just want clear and concise descriptions for specific settings and not a condescending "go read the man pages you fucking noob". I've been fucking with Linux for over a decade now; a lack of clear documentation is not my problem, and at this point is unacceptable.

    [–] subarctictundra@lemmy.world 0 points 1 month ago (1 children)

    I also wish Linux used a standardized config file format.

    [–] renzev@lemmy.world 0 points 4 weeks ago* (last edited 4 weeks ago) (1 children)

    Sounds like you're gonna love nixos

    [–] subarctictundra@lemmy.world 0 points 4 weeks ago* (last edited 4 weeks ago)

    I actually looked into it, although I didn't like very much that the config file is actually a program and an odd language. They should have used something commonplace like JSON

    [–] RejZoR@lemmy.ml 0 points 1 month ago (1 children)

    It's why I'm so furious about Linux in general and how every god damn intent to change almost any setting begins with "open Terminal...". I don't want to use the damn Terminal. It's 2025 now, put the god damn basic ass settings into control panel so I can click it without first spending half an hour to find a long noodle of commands for Terminal that I don't even understand, paste it in and hope for the best.

    Like, I had issues with Bluetooth module in my laptop and I wanted it disabled so my BT USB dongle is main. In Windows I'd just go to Device manager and disable that device. Done. On Linux I spent hours diging on how to disable BT module and weed out all the bullshit on how to disable the function itself because I need it, just not from the fauly module. Then I spent asking on Reddit where someone finally posted a working Terminal command that I had to save into config file using Terminal because file manager is to stupid to save it into system area by just asking me if I want it there or not. I now have a folder with config file and instructions on what stupid ass copy command for Terminal I need to use to copy the config file where it needs to be.

    Just so much unnecessary bullshit for something that could be done in literal 5 clicks at worst if the damn option was in GUI to disable single device on the system. Also fun fact, Linux has a "wireless devices" tool, command line one and it uses device ID to apply it and the fucking ID changes every time for the device so you can't make a permanent setting. I kid you not. I've never seen anything more idiotic.

    [–] renzev@lemmy.world 0 points 4 weeks ago (1 children)

    This is such a stupid take. Gui obscures the thing that you want to do behind endless buttons and menus and some bullshit that some self-proclaimed "user experience engineer" thought would be "intuitive". With cli it's like you're talking directly to the computer. Want to stop the networking service? service networking stop. Couldn't be simpler!

    Also fun fact, Linux has a “wireless devices” tool, command line one and it uses device ID to apply it and the fucking ID changes every time for the device so you can’t make a permanent setting.

    Are you talking about rfkill? Strange, for me the ID's don't change. But even if they do for you, what's stopping you from getting the ID just by grepping for the device name? Something like rfkill list | grep YOUR_DEVICE_NAME | cut -d ':' -f 1 | xargs rfkill block.

    [–] RejZoR@lemmy.ml 0 points 4 weeks ago (1 children)

    Calls it stupid take, proceeds to give me most absurd noodle of a commandline for something that could simply be a Enable/Disable button on a device list panel that every idiot with no prior knowledge of Linux, CLI or memorized command could do it. I think proved my point once again.

    [–] renzev@lemmy.world 0 points 4 weeks ago (1 children)

    It would take you less time to put together that one-liner than to find the correct button in an unfamiliar gui. How exactly does that prove your point?

    [–] RejZoR@lemmy.ml -1 points 4 weeks ago (1 children)

    BS, I looked online for hours and waited for replies on reddit and no one gave me this line. So, no, I'd in fact do it via GUI in minutes where it took me hours for some backwards config that doesn't look anything like this that made me do what I wanted. With extra steps to copy that stupid file into system folder, of course via stupid Terminal because I couldn't do it through file manager in any way. The level of stupid Linux has to configure trivial things is just astounding.

    And what's weird is how Linux purists always whine about it. Like, I don't care, keep using your stupid Terminal, just give me damn GUI for this basic shit. I don't want to waste time and memorize idiotic noodles of commands to do trivial shit. No one is taking away any of the stupidity you love, just give ME the choice. Instead the only choice is use of stupid CLI. Ugh.

    Also it's not "unfamiliar" GUI. It's called practical deduction. If I need to do this and this I already know I might need to look under this and that category in settings or just type rough related words in search and it would show me the setting. If whoever makes GUI isn't a complete moron, it would be easy to find. Good luck with any of that with CLI where you need to input exact command from start. Your logic just makes no sense.

    [–] renzev@lemmy.world 1 points 3 weeks ago (1 children)

    I don’t want to waste time and memorize idiotic noodles of commands to do trivial shit.

    Also it’s not “unfamiliar” GUI. It’s called practical deduction.

    Can you not see how the two arguments you're making are completely contradictory and self-defeating? Nobody is asking you to memorize "noodles of commands". What, do you think we all have little books full of shell one-liners for every task imaginable? You just have to know a few basics: The pipe redirects data, cut splits lines of text, xargs builds up arguments raw text, etc. Put them together in whatever way you wish to accomplish the task at hand. It's -- exactly as you say -- practical deduction.

    [–] RejZoR@lemmy.ml 1 points 3 weeks ago

    You're really not making the case in your favor with this argument. So, now I have to memorize even more dumb commands. What in the fuck? You really have no clue about GUI, do you? Youbdon't have to memorize ANYTHING, just have general idea in which category of settings to go. And that's it.