• 26 Posts
  • 568 Comments
Joined 8 months ago
cake
Cake day: January 29th, 2024

help-circle
  • I’m sure I’ll get shouted down for this suggestion by the haters, but I’m going to make it anyway because it’s actually really good:

    Use an Ubuntu LTS flavour like Kubuntu. Then, add flatpak and for apps you want to keep up to date, install either the flatpak or the snap, depending on the particular app. In my personal experience, sometimes the flatpak is better and sometimes the snap is better. (I would add Nix to the mix, but I wouldn’t call it particularly easy for beginners.)

    This gets you:

    1. A reliable Debian-like base that you only have to upgrade to new releases every 2 years
    2. Up-to-date apps, including confinement for those apps
    3. New kernels every 6 months (if you choose - you don’t have to, though)















  • as you can see on other comments I’m not alone with that stance.

    Being in the majority doesn’t necessarily make one right, as shown by [insert election result you disagree with here]. But if you actually are serious about that, you do realise how entitled it sounds to demand that someone do free work for you in the particular way you want it done?

    And I believe you mean prerogative.


  • lengau@midwest.socialOPtolinuxmemes@lemmy.worldSnap bad
    link
    fedilink
    arrow-up
    2
    arrow-down
    3
    ·
    5 days ago

    Because the separate installation means you can actually end up with both an apt installed and a snap installed.

    This is something that can happen any time you have multiple package managers or even multiple repositories in the same package manager. Google’s official Chrome apt repo has debs for google-chrome-stable, google-chrome-beta and google-chrome-unstable, quite intentionally.

    My comment about docker was a specific example of such a case, where vulnerabilities were introduced. It was actually a commonly used attack a few years ago to burn up other CPU and GPU to generate crypto

    Can you provide a link to a source about that? I can’t find anything about it.

    and you ended up with both a snap and apt installed docker

    If you installed both the docker.io package from apt and the docker snap, yes you wound up with both. Just as if you install both google-chrome-stable and chromium you’ll end up with two packages of (almost) the same browser.

    The fact that they are both packaged by Canonical is both irrelevant and a perfect example of the problem.

    Then I’m gonna ask that you elaborate what specific problem you’re trying to explain here, because these seem pretty contradictory.



  • lengau@midwest.socialOPtolinuxmemes@lemmy.worldSnap bad
    link
    fedilink
    arrow-up
    3
    arrow-down
    3
    ·
    5 days ago

    In both cases, the packages are owned by the same people? (Fun fact: mozilla actually owns both the Firefox snap and the firefox package in the Ubuntu repos.) I’m non sure how that “potentially introduces vulnerabilities” any more than “having a package which has dependencies” does.

    I’m not sure what you’re referring to with Docker. Canonical provides both the docker.io package in apt and the docker snap. Personally I use the snap on my machine because I need to be able to easily switch versions for my development work.


  • lengau@midwest.socialOPtolinuxmemes@lemmy.worldSnap bad
    link
    fedilink
    arrow-up
    16
    arrow-down
    3
    ·
    5 days ago

    If you don’t want to explain, you’re perfectly welcome to not explain. But saying what amounts to “if you don’t know I’m not telling you”, especially when you weren’t specifically asked, is a pretty unkind addition to the conversation.