this post was submitted on 19 Mar 2026
499 points (98.6% liked)

linuxmemes

30865 readers
1191 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, no politics, no trolling or ragebaiting.
  • Don't come looking for advice, this is not the right community.
    • 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
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    499
    Please help, I'm stuck! (infosec.pub)
    submitted 2 weeks ago by mech@feddit.org to c/linuxmemes@lemmy.world
    151 comments fedilink hide all child comments
    you are viewing a single comment's thread
    view the rest of the comments
    [–] insomniac_lemon@lemmy.cafe 1 points 3 days ago

    It’s pretty easy to uninstall and make certain packages taboo

    I remember reading that you couldn't turn it off unless you outright disabled recommended packages. Reading again, I see conflicting statements and it seems like a common thing people take issue with. Though even locking seems to me like it should just be something that happens during explicit removal, if that is a fix.

    So I still kind of hate stuff like that.

    Making a system either unresponsive or worse, broken. I feel it would be a workflow nightmare of a scale that would beggar belief and it would need constant attention from the maintainers…Something we’d probably not see in our lifetimes

    My system is currently outdated and mostly usable, but has 4 different application issues (1 crash, 1 flicker, 1 compiling/library error, 1 feature error)... before I stopped updating, rolling updates gave me a few bad rolls that did not fix some of these issues (and if I'd have rolled not even week later w/o reading the news, I would've been toasted into terminal-fix-it-now-land).

    So I'd say there's a lot of room for improvement here. I dream of something that works like this:

    • bin.fast: Major.minor.greatest, 7..30 days
    • bin.stable: Major.minor.greatest, 30..180 days
    • userspace: any version (including non-system package formats), total install/non-shared-dependencies size may influence update frequency (or budget)
      • small things may update always, big programs may even get to the point where it switches the install over to a bin version for you rather than compiling again
    • userspace packages may also slow down dependencies

    Non-critical applications may be updated less. Security updates or marked-as-needed-fix more. Alternatively, supporting explicit branches (like Godot's 3.X and 4.X) in official repos helps. Maintenance updates (nothing known broken) may be delayed if something seems/is-known wrong (build-bots, user reports or comments, upstream fix needed or dependency too new, admin/maintainer intervention etc)

    Ultimately, this could mean an update about every week or slower than once a month depending on packages and if the user encounters issues or not. And I'm sure this may be possible with some package system, but again not something default (and less effective if a package system doesn't provide the needed structure/information).

    Hardware wise, yeah I'm otherwise still pretty happy with the performance level I have (and it's a fine target for my own stylized projects, still working on that). A smaller(+more efficient) system would be nice, but GPUs seem to still be behind/lower-value than CPUs though. Polaris would be fine just to make things easier though, not that I want to buy a sidestep especially when the market is so stagnant. Same thing with workarounds that won't be really cheaper either (esp, w/RAM etc pricing).

    This is why I am very careful to use a small amount of them as there are a few apps

    What I'm talking about was an issue with 1 package due to sandboxing, and it was Krita IIRC (something I don't care about sandboxing on). I think KDE stuff was being pulled in too (I don't use it, but I do use Kate and few other things that use Qt).