• 0 Posts
  • 27 Comments
Joined 1 month ago
cake
Cake day: July 10th, 2025

help-circle


  • Honestly it sounds like you’ve mastered a completely new kind of operating system, based on Linux but evolving in its own direction

    Thanks for the compliment 😅. I do think there’s some truth in it being a new kind of Linux-based OS. But it’s not as big of a departure like say NixOS. Heck, I’d argue it’s grounded within a relatively basic premise: What’s the minimal amount of effort required to make our current Linux systems attain desirable qualities like being reprovisionable and anti-hysteresis? The whole bootc-shebang is just leveraging existing container technologies (I’m sure you’re familiar with Docker) to the Linux you run on your computer.

    and there’s probably only a handful of people using it at that level.

    If we would (perhaps arbitrarily) choose for “that level” to be “crazy enough to create and run their own image”[1], then it’s true that our numbers are probably only in the order of hundreds. Though, the knowledge required to build your own image is (almost) equivalent to the knowledge one ought to have to create their own OCI image; you know, the very same used for Docker, the container technology that represents a billion dollar industry.

    It’s pretty cool to learn more about, so I appreciate what you’ve had to say.

    I appreciate it. I like conversing with you as well 😊!

    I already know and love traditional Linux and don’t see a compelling reason to change

    That’s perfectly valid.

    I don’t think it’s the way to point a newcomer.

    Please allow me to explain why I differ on this:

    The beginner has no preconceived notion on how Linux is ‘supposed’ to work. As such, they will adapt to whatever you throw at it. Be it Mint, Arch or Fedora Atomic. Heck, it’s undeniable that out of these, Fedora Atomic works the closest like their phone. Which has undoubtedly become the most recognizable OS for your average Joe.

    FYI, Fedora Silverblue was my foray into Linux. The first one or two weeks definitely gave me a hard time, but that was over three years ago. If I was able to survive in such a ‘hostile’ environment, then newcomers should have absolutely no trouble getting onboard with the introduction of Bazzite (and the other uBlue images).


    1. As that’s most likely my biggest Fedora Atomic achievement. ↩︎



  • pyssla@quokk.autoLinux@lemmy.mlfirst time using linux, how screwed am I?
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    edit-2
    18 hours ago

    You do sound obtuse.

    Hehe :P . Please feel free to clarify what you meant with the repos being limiting (or something). I’m genuinely interested to know. See Edit down below

    I still think bazzite is the wrong suggestion for newcomers

    It’s your absolute prerogative to believe/think/state whatever you wish. However, I don’t think you’ve yet made a convincingly compelling case. You absolutely don’t have to, but if you’ve got more to say on the subject matter, then please do so for the sake of (potentially) enlightening others.

    I don’t care if you like my opinion.

    Good…, I suppose. Neither should you care anyways 😜.


    Edit: I only now noticed that you had edited your previous post. My apologies.

    Having access to the AUR allows me access to much wider array of software.

    Agreed. I also occasionally access stuff from there through my dedicated Arch distrobox. I occasionally make use of my Ubuntu distrobox, or Alpine distrobox as well. Thanks to Distrobox (and similar technologies), it has become an absolutely glorious experience to not be limited by the distro’s repos. Instead, I can make use of whatever repos are out there. Granted; Distrobox is not exclusive to Fedora Atomic, but you’d be hard-pressed to find another distro on which it works as well as it does on uBlue’s offerings.


  • Thank you for the quick answer and for providing clarifications!

    I would say the greatest limitation would be repos

    What do you mean? What’s wrong with Fedora’s repos? Apologies if I sound obtuse*.

    and your ability to build whatever software you want from source.

    There’s nothing preventing you from doing this within a container created by Toolbx/Distrobox. I can attest to this. You can even build it natively. While I haven’t personally engaged in building it natively, I can’t imagine it would cause any problems. But please correct me if your experience (or otherwise) is different.

    Can you run Hyprland and all of its companions like hyprlock, hyprpaper, etc on bazzite? That’s the setup I prefer, and I’m fairly certain it’s not possible in a Fedora based immutable system.

    Fam, break your leg. Nothing is stopping you; someone else has already done just that. And you can just piggy-back of their effort. In case you’d like to see other (successful) attempts at making Hyprland work on Fedora Atomic: consider taking a look at wayblue and hyprland-atomic.



  • pyssla@quokk.autoLinux@lemmy.mlfirst time using linux, how screwed am I?
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    1
    ·
    edit-2
    19 hours ago

    They are extremely limiting

    Assuming you’re referring to Fedora Atomic, your statement is extremely exaggerated. Out of the top of my head, the current limitations are iffy akmods and UKI/systemd-boot. The latter of which is being worked on currently and might arrive rather sooner than later. Neither of which I’d assume 95% of Linux users ever engage with anyways…

    add multiple complications to otherwise simple tasks

    I feel like you don’t know what you’re talking about. Please be explicit; which tasks are made more complicated on Fedora Atomic?

    the padded cell of immutability means you can’t really fuck around and learn how traditional Linux systems work

    It’s true that you aren’t supposed to “fuck” around (most of) /usr during runtime. Furthermore, I agree that the existing ways to circumvent/bypass this leave much to be desired. But, again, most peeps use perfectly fine systems without ever feeling the need to tinker with /usr… And if you absolutely must…, well…, Fedora Atomic doesn’t actually stop you. It just wants you to adhere to its ways of achieving it. Making it more of a paradigm shift, rather than outright limiting the user.

    If your criticism basically boils down to “I can’t make use of my preconceived notion on how Linux works.”, then “Yes.”; that’s exactly the point. Granted, it wouldn’t hurt if Fedora Atomic allowed conventional methods to continue working. But as it’s currently in the middle of a architectural shift (going from rpm-ostree to bootc), I’d argue they’ve got more important things to work on.


  • If you’re the type of new user that likes to go balls deep straight away, then Arch is arguably one of the better options thanks to its excellent Wiki. However, please don’t blatantly overestimate yourself for the heck of it. Consider checking out ArchWiki’s own entries on this matter:

    i found a tutorial on it with 3 - 4 pages full of text and was a bit overwhelmed

    I don’t think this attitude is helpful for conquering Arch, but YMMV.

    recently i just finished building a new pc. mostly for gaming since my only exposure to linux is steam os and i heard its uses arch with kde plasma so i try to emulate it as close as i can.

    FWIW, if you just want to emulate SteamOS, perhaps consider Bazzite instead. It’s not based on Arch, but it arguably is the closest to SteamOS (but better). More so than any Arch-based distro*.




  • pyssla@quokk.autoLinux@lemmy.mlLingmo OS???
    link
    fedilink
    English
    arrow-up
    2
    ·
    10 days ago

    That can be a double-edged sword, especially if the distro has been around a long time. What the user finds can be out of date and now just plain wrong. Ubuntu definitely suffers with this.

    Excellent point! Thank you for mentioning this! I feel this is often overlooked for reasons I don’t understand. Thankfully, we can teach (new) users how they can navigate around this: e.g. by mentioning the version of the distro within the search query OR by simply being wary of old(er) info.



  • pyssla@quokk.autoLinux@lemmy.mlLingmo OS???
    link
    fedilink
    English
    arrow-up
    3
    ·
    11 days ago

    OP is still a very new Linux user (if at all) that hammers on stability in every one of their posts. My comment was written with that in mind. But, even in its current version, it isn’t absolute and leaves room for nuance/exceptions by using terms like “(almost)” etc.

    Veteran users with awareness of the Linux landscape are somewhat able to discern the upcoming serious projects with a future from the to-be abandonware. FWIW, I’ve championed distros like Bazzite (and its uBlue siblings), CachyOS, Nobara, PikaOS and secureblue far before they had any serious recognition (if at all). So I’m definitely with you that promising projects deserve adoption, support and more.

    And let’s be honest, if a distro is a one man or small team project, mass adoption is no guarantee of longevity.

    Agreed. I believe the “somewhat” I used alludes to that. One might argue that the concept of absolute guarantee doesn’t exist. Even with Arch and Debian*; though I’d argue they come closest IMO. Nevertheless, there are definitely gradations between Arch/Debian and a student-owned hobby project that was created just today.

    Mass adoption is a relatively easy metric to gauge. And (often) comes with tons of support/discussion across the internet that will prove to be useful for the new user.

    Please feel free to provide other metrics that OP or others might appeal to.


  • pyssla@quokk.autoLinux@lemmy.mlLingmo OS???
    link
    fedilink
    English
    arrow-up
    9
    ·
    11 days ago

    Some looking around suggests that the distro is just over 6 months old or so.

    Even if it does literally everything right, longevity is only tested with the passing of time. To exemplify this, let’s go back in time… Relatively short after I made the switch to Linux, there was a lot of buzz around risiOS. Unfortunately, it didn’t take long until this exciting new project stopped receiving any further development. And, as far as I can tell, its creator has literally moved on to their next project.

    The above example ain’t unique, though. Heck, I’d argue that the coming and passing of projects is the expected pattern. The projects that remain relevant and continue to receive development are the actual anomalies.

    All of which is just to say that it’s (almost) ill-advised to prefer a new project over a well-established one. Only after a (relatively) new project receives mass adoption, like what we currently see with Bazzite and CachyOS, does it become somewhat of a safe bet. Even if only for the foreseeable future*. Until then, you’re at the mercy of the whims and continued interest of a single developer (or a very small team).

    Going back to Lingmo OS itself, I suppose its main appeal lies within its unique aesthetics. I’m especially fond of their macOS-like global menu found within its top bar. The now-defunct CutefishOS also had something similar going on… Which brings us back to our earlier point on longevity. Aight, verdict: honestly, I don’t think it’s necessarily more aesthetically pleasing than say GNOME or KDE Plasma. At least to me*. As such, I understand that I’m not the target audience. Nor do I think that you or anyone else should be swayed by this (or similar projects) on aesthetics alone.




  • Based on their post history, I strongly suspect the OP has English as a non-primary language.

    While I believe your intent and attempt is noble, in OP’s comment history we find their admittance to being American.

    Furthermore, I’d argue their history actually suggests that they’re very much capable of writing perfectly sound English. In fact, this isn’t my first interaction with OP. So I know they can do better. But, for whatever reason, they haven’t demonstrably shown the same diligence when writing up this particular post.

    They are doing fine, their posts are perfectly understandable.

    The bold part is probably directly targeting the “proofreading your writings before posting them”-part of my original comment. And I’ll admit that I should have done a better job at conveying that this doesn’t intend to allude to a structural problem. So, to be clear, it was meant as general advice after being bothered by (only) this post.

    Uno Reverse

    Outwardly suspecting ESL for native speakers ain’t nice either, but I digress…


  • Fam, I loathe saying this, but -please- if you desire engagement, then at least put some honest effort into proofreading your writings before posting them. I’m just assuming stuff at this point because I can barely grasp your intent/writing. *sigh*

    Why do atomic distros which are supposed to me more stable, superior to some degree immutable environments lack good backup options? You can hack things together and there are somewhat installable tools. Like timeshift or etc etc.

    Which distros even come by default -so installed OOTB- with “good backup options”? Which atomic distros is this statement even based on?

    But it seems they place a lot more emphasis on rolling back poor updates in the event than total system backups.

    Because their atomicity barely goes beyond updates. The ‘atomic’ in “atomic distros” mostly describes how its updates are atomic; i.e. the system either updates successfully or doesn’t update at all. Thus, by design, we have two possible states after an update: a ‘successfully’ updated system or a ‘failed’ update resulting in the same state as the previous. Atomic distros aren’t smart enough to catch all ‘breakage’ occurred by ‘successful’ updates. As such, most of these breakages will only show them after trying to boot into updated system. Deleting/erasing the previous known good state without verifying that the new/upcoming state works well is foolish. Especially on a distro that’s got robust updates otherwise. Hence, the functionality of rollbacks on updates is almost trivially done/applied to atomic distros, as it (almost) follows by design.

    So, what I’m interested in is the following:

    • Are you familiar with the notion of stateless systems? Is this (perhaps) what you’re (actually) seeking?

    By default it you should have true backups then layer in rollbacks. Not the other way around. Am I missing something?

    I think my previous paragraph should be enlightening in this regard. If you disagree (or something/otherwise), then please feel free to elaborate why you think so. Btw, what do you even mean with "true backups?