• 11 Posts
  • 50 Comments
Joined 1 year ago
cake
Cake day: August 8th, 2023

help-circle

  • I’ll be honest here: I switched my main laptop from slow roll to Linux Mint to install it several months back to install wayDroid. I’ve been happy with the switch. Here are my thoughts:

    1. I’d installed Linux Mint + wayDroid on the laptop of various family members, and really liked what I saw
    2. Runa-chin has done a great job providing instructions and packages to install it on tumbleweed, but it has quirks that I didn’t feel like fighting. It just works out of the box in Mint.
    3. I like having KDE plasma 6 on slow roll, but the cosmetic difference from plasma 5 is minimal (it’s more performance/longer term). I’m ok with sticking with plasma 5 if I get a painless wayDroid installation
    4. Slow roll is generally stable, but updates have burned me a few times in the past year. More stability is always nicer
    5. Flatpak + appimage + snap (yes, I don’t mind using whatever is officially recommended on the project website of whatever I’m trying to install, though it would be nicer to have more official flatpaks) make it such that while my base is stable, I can still get some pretty recent packages










  • Why not try it for yourself on Linux mint first by installing plasma? Plasma 5 is available on mint - I believe Fedora has plasma 6.

    I use plasma 6 on my Opensuse Slowroll laptop and plasma 5 on my LMDE desktop.

    Overall, I’ve found plasma 6 to run slightly better (I was on plasma 5 on Slowroll too for a long time).

    Once you install and try plasma 5 on your current install, that will be a much less disruptive way to see how well it works for you.

    After ricing, both plasma 5 and 6 are pretty similar on my setup. The cube desktop effect isn’t there by default on plasma 5 of course.





  • GravelPieceOfSword@lemmy.caOPtoLinux@lemmy.mlFwupd Will Use Zstd Compression
    link
    fedilink
    English
    arrow-up
    5
    arrow-down
    1
    ·
    edit-2
    8 months ago

    As with all definitions, there is a gray area where people will have different boundaries on exact meanings. To you - a supplier relationship needs an explicit payment, which is a fair definition.

    However, the more widely used definition that most people, including me, refer to, is not necessarily focused on the supplier, but on the supply - what we use in our toolchains is a supply - regardless of how it was obtained.

    When there is an issue in a trusted supply, even if it was not a commercial relationship (a prerequisite by your definition), it is a supply-chain attack by the more widely used definition.


  • The article states reasons which aren’t limited to what happened. I understand and agree with your sentiment about the supply chain issue being something that could happen anywhere - those were my initial thoughts too.

    The reasons for shifting are related to speed, other mainstream software already having made that switch years ago (pre incident), and unfortunately… More robustness in terms of maintainers.

    Open source funding and resilience should be mainstream discussions. Open source verification and security reliability should be mainstream discussions: here’s a recent mastodon thread I found interesting:

    https://ruby.social/@getajobmike/112202543680959859

    However, people switching from x to z (I did see what you did there) is something that is going to happen considering the other factors listed in the article that I summarized above.


  • Linux mint Debian edition or Opensuse tumbleweed.

    Slow Internet/less updates, older, more tested software, slightly wider package availability: LMDE.

    Faster Internet, more updates, very new (but well tested) software, needs slightly more technical knowledge sometimes: Opensuse tumbleweed.

    I personally use Opensuse Slowroll, which is a slower rolling release experimental version of Opensuse tumbleweed.




  • I run KDE on opensuse Slowroll - Intel i9 processor with plenty of RAM.

    Check btrfs snapshots, and consider disabling them if you don’t really need them.

    Here’s my story some time in the recent past:

    Similar freezing issues that got more frequent. I have network and CPU monitor widgets on my desktop, and noticed my CPU usage peaking during freeze.

    Ran top, saw #btrfs was doing a lot of processing. It was running snapshots.

    I’d like snapshots, but a responsive system is more important to me: I have frequent backups of most of my stuff anyways.

    Once I disabled btrfs snapshots, I stopped having the periodic freezes (which I also noticed were often some time after system/flatpak updates).