• 2 Posts
  • 44 Comments
Joined 1 year ago
cake
Cake day: July 9th, 2023

help-circle


  • You asked how it works, the post states how it works. You also asked if it’s slow, which is clearly answered in the post (though you didn’t quote that part). You also asked if there’s some “secret sauce” allowing it to be fast, which is also a weird question since everything used is listed in the post.

    If something wasn’t clear to you, why not specifically ask about it? Even in this comment, you still don’t specify what you don’t understand. What kind of answer are you expecting to get?



  • (Note that the immutable distros will only be represented by Fedora, GuixSD and NixOS. The others are either too niche or immature)

    This was my issue with your original comment - I’m aware most of the work on features like these is based on immutable distros, but just being immutable doesn’t mean it will have those features.

    When it comes to reproducibility and declarative system management, I think you’re right that they’re only available in immutable distros.

    The security benefit of a read-only filesystem isn’t very significant IMO, and for some immutable distros, interesting parts (to attackers, like /etc for example) are mutable anyway.

    And I don’t use any snapshot solution currently, but don’t most of them only store the parts that change between snapshots? According to the Arch Wiki, Snapper’s “default settings will keep 10 hourly, 10 daily, 10 monthly and 10 yearly snapshots”. This doesn’t seem like much of an advantage for immutable distros, really.

    There’s no need to go over the “consequences” as they’re (as the name implies) consequences of what has mentioned earlier. Hence, as their causes are better than the one found on traditional distros, so are the consequences better than how they’re found on traditional distros.

    I disagree with this though. “Better” is very subjective - I for one consider being able to have an up to date system that can have parts of it updated without rebooting to be much nicer than using something like rpm-ostree, even if it is safer to use in theory (I can’t remember the last time I had an issue when installing a package; rebooting to apply an install atomically will likely make no difference to me other than wasting my time). I know I can use containers to get around this, but once again, this just adds to the hassle.


  • I guess I’d define it as a distro where the base system is read-only and changes or updates to it are done by replacing it atomically.

    Fact of the matter is that the immutable variants of these features are far and wide superior over their counterparts found on traditional distros.

    How exactly? Just saying it doesn’t make it true. Except for atomic updates (which are basically the main point of these distros, and why they’re also called “atomic”), what can they do that you can’t on a normal distro?





  • dsemy@lemm.eetoLinux@lemmy.mlUltramarine Linux 40 Released!
    link
    fedilink
    English
    arrow-up
    71
    ·
    6 months ago

    Ultramarine Linux was created out of frustration with the legal limits of Fedora. As Fedora (and Red Hat) is an American entity, there are legal restrictions on what software can be packaged in the distribution due to the US patent system.

    The Ultramarine team aims to make Fedora a little more user-friendly by allowing users to install or package any software they want as long as someone maintains it in Flathub, RPMFusion, or Terra.

    In addition to this, we provide various UX improvements around the system, and in the future, custom apps.

    In case anyone else was wondering what this is





  • A much larger problem is that the energy consumption is several orders of magnitude larger than that of our brain. I’m not convinced that we have enough energy to make a standalone “AI”.

    This is a major issue I have with basically anyone who talks about current “AI” systems - they’re clearly not even close to AI, as they require an extreme amount of energy and data to perform tasks which would be trivial to an actual brain. They seem to lack any ability to comprehend their input, only mimicking it through brute force, which is only feasible since computers got fast enough and we can currently keep up with the energy demands.


  • As far as I’m aware, no launcher (in the style of KRunner) exists which has all those features.

    With some effort, you could implement a lot of this functionality using a “generic” launcher (like rofi, for example), but integrating a system tray will be close to impossible (unless you’re willing to write a program which acts as a system tray and provides those launchers with enough information to display a useful representation of the tray, could be cool).