en.osm.town is one of the many independent Mastodon servers you can use to participate in the fediverse.
An independent, community of OpenStreetMap people on the Fediverse/Mastodon. Funding graciously provided by the OpenStreetMap Foundation.

Server stats:

258
active users

#atomicdesktops

0 posts0 participants0 posts today

I've completely reworked how I build the sysexts for Fedora Atomic Desktops, Fedora CoreOS and other image based Fedora systems.

We now have a pretty website listing them: extensions.fcos.fr

This is still an unofficial/experimental project but it has been working well for me for a while now.

Next step: writing a manager for all those sysexts to make installing/removing and updating them easier.

extensions.fcos.frsystemd system extensions for Fedora image based systemsExperimental systemd system extensions (sysexts) for Fedora image based systems

I will be presenting at Flock to Fedora in Prague this June about the Fedora Atomic Desktops, the future plans and what would be needed before we can make them the default option.

If anyone is interested in sharing an hotel room with me to save on travel cost, feel free to reach out privately. I'll book the hotel soon.

Continued thread

For users who want to try #Linux, I recommend this: Do not listen to people who tell you to use #Ubuntu, #LinuxMint or other variants. They all use the same complex and often breaking mechanisms, and can cause a lot of hassle.

Instead, I recommend these systems:

- #Fedora #AtomicDesktops
- #UniversalBlue #Aurora #Bluefin #Bazzite
- #HeliumOS

Looking forward to #SerpentOS too, and trying #NixOS.

These systems are reliable like an Android phone, while offering you more freedom.

I just found a trick!

How to reinstall packages in #Fedora #Atomic desktop #downstream images like #uBlue (#Bazzite, #Bluefin, #Aurora, #uCore) or #Secureblue, that were removed in the image building process.

There is a bug in #rpmostree, that basically prevents you from reinstalling #Firefox if the builders decided to remove it.

github.com/boredsquirrel/Linux

universal-blue.discourse.group

I'll be at FOSDEM this weekend! I'll be giving a talk with Allison on composefs and how it fits well for image based systems: fosdem.org/2025/schedule/event

Feel free to reach out if you want to meet and chat about Fedora CoreOS, Atomic Desktops, sysexts, KDE or Flatpaks. I'll likely hang around the image-based, container or Rust dev rooms.

fosdem.orgFOSDEM 2025 -
Replied in thread

@NetscapeNavigator

I think a distro is only measured by
- how well do upgrades work
- does it auto-update well and reliably
- does it break after 2 years or so of intense use?

And #dnf #Fedora is pretty bad in all of these in my experience. Fedora atomic desktops are pretty great.

But only #ublue has good autoupdates. The "GUI stores should do the updates" ideology will likely stop automatic updates from working well for another few Fedora releases.

Fedora 41 Beta has been released! 🎉
fedoramagazine.org/announcing-

TL,DR: Hold on a bit before using bootupd on the Atomic Desktops and IoT.

We still have one major bug that will break systems upgrading from Fedora 40. The fix should land hopefully in tomorrow's update.

This only impacts updated systems and does not impact fresh Fedora 41 installations.

More details about bootupd support in: fedoraproject.org/wiki/Changes

Fedora Magazine · Announcing Fedora Linux 41 Beta - Fedora MagazineAnnouncing Fedora Linux 41 beta and describing what is new

Manual action needed to resolve boot failure for Fedora Atomic Desktops and Fedora IoT.

Since the 39.20240617.0 and 40.20240617.0 updates for Atomic Desktops and the 40.20240617.0 update for IoT, systems with Secure Boot enabled may fail to boot if they have been installed before Fedora Linux 40.

Details in fedoramagazine.org/manual-acti

Fedora Magazine · Manual action needed to resolve boot failure for Fedora Atomic Desktops and Fedora IoT - Fedora MagazineHow to resolve boot issues on systems with Secure Boot enabled which may fail to boot if they have been installed before Fedora Linux 40

Due to a bug in rpm-ostree, the '/etc/[g]shadow[-]' files in Fedora CoreOS, Fedora IoT and Fedora Atomic Desktops have the world-readable bit set.

To fix impacted systems immediately, run the following command as root:
$ chmod --verbose 0000 /etc/shadow /etc/gshadow /etc/shadow- /etc/gshadow-

For more details, notably the full list of affected versions, see: github.com/coreos/rpm-ostree/s

GitHubWorld-readable /etc/shadow, /etc/shadow-, /etc/gshadow, /etc/gshadow-# Impact The `/etc/shadow`, `/etc/shadow-`, `/etc/gshadow` and `/etc/gshadow-` files in a default build have the world-readable bit set. This only impacts commits built with rpm-ostree start...