[–] 5 points 1 week ago

No it's not. Fedora got pedantic about the term "immutable" but there are more than a few that use Atomic or Immutable and they are different things.

Atomic is all-or-nothing upgrades, Immutable is a read-only OS structure (this is what Fedora got picky about as being ambiguous).

  • source
  • parent
  • context
  • [–] 9 points 1 week ago

    Atomic is all-or-nothing upgrades / block upgrades instead of individual packages

    Immutable is a read-only operating system root (yes, you have access to /etc, fedora got pedantic about this)

    You can have one, the other, or both, or none.

    See my reply to OP for sources but there are more than just the two I referenced.

  • source
  • parent
  • context
  • [–] 3 points 1 week ago

    Atomic is all-or-nothing upgrades / block upgrades instead of individual packages

    Immutable is a read-only operating system root (yes, you have access to /etc, fedora got pedantic about this)

    You can have one, the other, or both, or none.

    See my reply to OP for sources but there are more than just the two I referenced.

  • source
  • parent
  • context
  • [–] 6 points 1 week ago* (1 child)

    No, they aren't. I feel like I'm taking crazy pills reading these comments.

    Atomic is all-or-nothing upgrades / block upgrades instead of individual packages

    Immutable is a read-only operating system root (yes, you have access to /etc, fedora got pedantic about this)

    You can have one, the other, or both, or none.

    https://ubuntu.com/blog/ubuntu-core-an-immutable-linux-desktop

    https://fedoraproject.org/atomic-desktops/silverblue/

    What is an immutable operating system? Before we can discuss what differentiates Ubuntu Core from other immutable operating systems, we must first define the properties that make an OS immutable:

    Read-only: The primary characteristic of an immutable OS is that the running system cannot be directly modified by users or applications.

    Atomic updates: Updates are applied atomically; meaning they’re successfully applied all at once or not at all.

    [...]

    Edited for formatting.

  • source
  • parent
  • context
  • [–] 5 points 1 week ago (2 children)

    I have a m1pro, and it's pretty solid with kde. hdmi out does work through the port, but display port alt (over usbc) doesn't yet. 120hz refresh is working though, and it's just nice to have the macbook build quality with a good os.

  • source
  • parent
  • context
  • [–] 1 point 1 week ago (1 child)

    Well I'm happy with the suckless terminal, lol. No need for bells and whistles, and it takes like 17MB of RAM.

    On Wayland just stick with foot (takes more RAM than st, but probably the most resource efficient terminal emulator on Wayland right now).

  • source
  • parent
  • context
  • [–] 7 points 1 week ago* (3 children)

    have an M1 MBA, got tired of macos trying to trick me into installing the AI frosted glass edition number of the year variant. Decided I'd rather risk bricking my mac than end up with a device that locks me into AI.

    It works really well. I think I booted back into macos once to just grab my files to a usb and move them over to the new install (you can't remove it, you just get a separate partition for asahi and it has the ability to autoboot to asahi).

    I have faced 2 issues in the entire time, and one of them I half had with macos.

    1. usb c to display out is just not here. like at all. on macos, I could get it to work, but sometimes I needed to replug in a cable, or restart the monitor, and then it was stable, but it really took away the whole seemless 1 cable to have a docked setup simplicity I hoped for.

    2. I had a failed install once. Honestly might not even be related to Asahi. I don't know how the deeper kernel stuff works. Was getting total black screen on boot. no signs of life but my backlit keyboard after the Uboot logo and stuff. But after being scared it got bricked, I slept on it, looked up how to get a terminal up, tried it. It worked. I had to translate the key combo and hold down the fn key to properly hit F2 but it worked. I updated from the terminal, it did a total reupdate, reboot, and bang, worked like a charm after that.

    I have not upgraded to asahi 45 yet. kinda haven't wanted to hear my mac make its reboot sound twice like I have to for every update, but I have trust it'll work. No urgency though since no usb c display out, which is my only real desire in an update (aside from reg security patches)

    edit: here is a link to the device support: https://asahilinux.org/fedora/#device-support

  • source
  • parent
  • context
  • [–] 12 points 1 week ago

    Cannot wait for the news that SUSE becomes the latest target of exploits and such due to vibed cuck code... all because they fired people who knew how to do their job correctly for "AI and automation".

    We need no nonsense leaders who will do everything in their power to kill generative AI like centuries ago. Another project is slowly killing itself by a thousands cuts by a radioactive knife.

  • source
  • [–] 2 points 1 week ago

    we are talking abou specificly security updates, upstream for most projects that are important for security have a concept of LTS releases, e.g the kernel's LTS, debian updates their stable packages rellying on upstream's LTS, debian does sometimes switches to newer LTS releases even if it means breaking the no new feature general rule of thumb, e.g kernel LTS goes EOL, debian maintainers sometimes do try to backport fixes themselves but generally debian prefers to follow upstream's LTS EOL where possible, generally updating to the oldest LTS not in EOL yet

    debian has a specific team dedicated to security, updating packages, contacting and colaborating with upstream, reporting potential vulnerabilities e.g the xz backdoor first was reported to the ssh package maintaince team from which the importance and the nature of the issue was discovered and then reported to the debian security team which confirmwd the findings and made reports to other teams and tried contacting the old owner of xz since xz was effectively taken over by the malicious actor

  • source
  • parent
  • context
  • [–] [S] 0 points 1 week ago* (last edited 1 week ago) (2 children)

    Same thing, both words describe the same thing.

    EDIT: I have learned not only from the dude below me, but also more reading online that indeed atomic and immutable are not exactly the same thing. Related but different. Tho my comment stands I still like the atomic nature of Bazzite, but I also LOVE the immutable part of it.

    TLDR: Immutable means the core OS is read-only while it’s running, and atomic means updates swap in a whole new system all at once, so you can always roll back.

  • source
  • parent
  • context
  • Yeah I've read good things as well. I'm not familiar with Arch at all, but it sounds like Cachy might be a good stepping stone. I did Ubuntu for many years, bazzite just recently and only because it was less intimidating than Cachy when I just wanted to get it up and running haha. But now that I've settled in, I find myself thinking I might try dual booting it just to see 🤔

  • source
  • parent
  • context
  • [–] 1 point 1 week ago*

    I ran sid in serious production when I was younger and more foolish. The trick with unstable distributions is to test before you deploy and know the incompatibilities and have the fixes ready in advance. The problem is you are basically taking a snapshot approach and doing the work of the debian release system yourself and doing it half-arsed. An urgent security update comes out and you can't rush to deploy it without risking a dependency being pulled in that breaks under your config. For servers it ends up being a huge amount of work for no gain and you can actually miss out on security updates.

    BTW this approach is why Valve can release Steam OS based on Arch or Google can base ChromeOS on Gentoo and release them to millions of consumers safely. They freeze updates to create a release candidate and test it and they deploy a limited subset of packages.

    At home I update one arch desktop machine to work out what breaks, how to fix it and seed the package cache on our server before I do the rest and break everyone's systems. I could do the same with Sid but Arch, despite being unstable intentionally isn't all that unreliable compared with Sid though my experience with Sid is dated.

  • source
  • parent
  • context
  • [–] 5 points 1 week ago* (last edited 1 week ago)

    I only ever deploy and develop on Debian. Community run distros all the way. I had bad experiences with Redhat decades ago and do everything I can to avoid it or its siblings.

    Debian has faults but it is often a taste thing. I like systems that give me upstream with minimal patches, like Arch. I moved to Arch on all desktops/laptops. The Debian devs repeatedly doing dumb shit with ssh patches was part of that. Arch is not unreliable but it is unstable. All that means is that software updates which aren't backwards compatible sometimes require intervention . To be clear that is not a fault with Arch but it does make it much less suitable for long hassle free server deployments. Also Arch doesn't have the Debian security announce list or maintain a stable production environment for years with backported security fixes and unnattended security updates.

  • source
  • [–] 2 points 1 week ago (1 child)

    Honestly, after I saw this, I decided to look for alternatives that fit my use case and failed. All I want is a terminal where I can create splits and tabs in the same cwd as the current terminal even on a remote machine. I frequently want to create ad-hoc splits when working on a remote server. In kitty I can do this with a simply keystroke without any custom code or configuration, so long as I am using the ssh kitten. Are there any other terminals that do this? Bonus points if it implements kitty image protocol, which is used in a neovim plugin I use.

  • source
  • parent
  • context
  • [–] 3 points 1 week ago (1 child)

    Random freezes during gameplay, games sitting on the Steam loading screen and never starting (restart steam deck and they load straight away),

    Poor performance in kodi, taking 5 minutes or longer to load media list, video stuttering, audio not working on particular files.

    Re-flashing steam os never solved anything, but just recently went with bazzite instead and it's working nicely.

  • source
  • parent
  • context
  • view more: ‹ prev next ›