• 0 Posts
  • 26 Comments
Joined 12 days ago
cake
Cake day: February 28th, 2026

help-circle
  • do you stick with the same distro across your PC, laptop, and server, or do you pick different ones based on the device and what you’re doing?

    Definitely the latter.

    constantly have to look up flags for different package managers.

    FWIW, you don’t have to choose the distro’s package manager. While it makes sense in most cases, it’s definitely not a requirement. And that’s where the nix package manager comes in. Unbeknownst to some, you don’t have to be on NixOS to access it, simply because it’s probably already found in the repository of the distro you’re using. So, frankly, you can even expect that it’s well-supported.

    I feel like NixOS might be the only distro that could realistically handle all these use cases

    FWIW, containerfiles used in conjuction with bootc to boot your OS from, do allow differentiation within a single containerfile; i.e. specific changes are only applied for the designated target. This is accomplished by virtue of a single containerfile being able to produce many (very) different container images to boot from. So, in short, other avenues exist and bootc happens to be one I know. Note that bootc doesn’t (necessarily) push you towards Fedora(-derivatives). Despite being very new (and perhaps somewhat experimental), Bootcrew does provide container images for other distros; some of which have already spawned multiple derivatives of their own. See e.g. Tartaria and XeniaOS.

    but I’m a bit scared of the learning curve and the maintenance work it’d take to migrate everything over.

    My 2 cents: if you’re interested in NixOS, just start out with installing nix on any distro. And see where that takes you ;) !




  • Sorry to say, but there’s a lot questionable stuff found within your comment. But I will try to limit the discussion around some of the more egregious ones.

    Hate to keep litigating this around here, but the shift alone is enough. Explaining to people WTF an immutable filesystem is, is a sure way to frustrate them into giving up, despite whatever comms finesse you might THINK you have.

    I don’t understand what’s so hard to understand about (some) core system files being read-only, i.e. you can’t change/modify it. Can you help me understand why that would cause so much frustration?

    Counterpoint: STOP SUGGESTING IMMUTABLE DISTROS TO NEW USERS

    Countering the counterpoint with an anecdote: I cold turkey switched from Windows to Fedora Silverblue almost 4 years ago. Beginner-friendly derivatives like Bazzite (or other uBlue images) weren’t even around back then. And, somehow, I managed. And there are many other testimonials that point out something similar, especially with many[1] newbies appreciating Bazzite. Are you ignoring this empirical evidence? If so, on what basis?

    there is ZERO benefit

    Come on, you know that’s not true. Perhaps you intended to write: I suppose there is ZERO benefit to me (and others like me). Though, if you genuinely don’t know any, then please consider going over this (lengthy) blog post by Colin Walters, a key figure in the past and current development of Fedora Atomic and Fedora CoreOS. It’s not a very efficient writing for educating oneself on this topic, but it’s the best I know.


    1. Please, consider going over to the Bazzite subreddit and see it for yourself. ↩︎




  • I’m obviously not an expert. But, from what I can tell, the scene seems quite healthy. And I don’t see a reason why it wouldn’t thrive further. Especially as the Linux market share is in the lift. Anti-cheat shenanigans are a lot more concerning. Though, I’m optimistic that Valve is actively making progress on that front.

    Btw, just as an FYI: I know people that were more interested in software piracy. But I digress…







  • My priorities:

    • Secure. Unlike popular belief, the fact that the worlds infrastructure basically runs on Linux does not imply that your average Desktop Linux distro enjoys the same level of scrutiny when it comes to its security. Hence, the security-conscious should carefully pick a distro that can handle their threat model. Or, at least harden it to their liking.
    • Stateless. Conventionally, you will be met with a (relatively) minimal system after installation. After which you’re expected to configure it to your liking and go smooth sailing afterwards. Occasionally, you might (un)install stuff and/or modify settings; but nothing out of the ordinary, really. While applying some of these changes might seem trivial, they (kinda) lead your system to accumulate cruft. This cruft might seem innocuous, but it’s exactly why your system seems so fresh after a reinstall. Foregoing this altogether is referred to as going stateless. This is done by declaring a desired state and ‘flushing’ all changes that have not been declared. Many other benefits are associated with this, but I digress…

    The above[1] already dictates the use of NixOS with the impermanence and nix-mineral modules.


    1. So, without even going into release cadence etc. ↩︎