Tony Agudo
@antoniusmisfit.bsky.social
https://mstdn.social/@antoniusmisfit
https://github.com/antoniusmisfit
Open source and public domain software aficionado.
https://github.com/antoniusmisfit
Open source and public domain software aficionado.
Which makes my idea of putting systemd and GNOME in a specialized container environment the smart response for non-systemd distributions. But I have to give Adrian credit here: He's dropping the mask and literally telling non-systemd distros "just give in". Yeah, that's not gonna work.
November 10, 2025 at 5:02 AM
Which makes my idea of putting systemd and GNOME in a specialized container environment the smart response for non-systemd distributions. But I have to give Adrian credit here: He's dropping the mask and literally telling non-systemd distros "just give in". Yeah, that's not gonna work.
And one last thing... I object to anyone calling GNOME "The Linux desktop". GNOME is "a Linux desktop". That is, merely one of many: KDE, XFCE, MATE, Cinnamon, LXQT, Cosmic, Budgie, Deepin, and numerous window manager environments. GNOME does not have a monopoly on the Linux desktop space.
November 8, 2025 at 4:03 PM
And one last thing... I object to anyone calling GNOME "The Linux desktop". GNOME is "a Linux desktop". That is, merely one of many: KDE, XFCE, MATE, Cinnamon, LXQT, Cosmic, Budgie, Deepin, and numerous window manager environments. GNOME does not have a monopoly on the Linux desktop space.
But after some thought... Dropping GNOME is probably the best choice for non-systemd distros. If GNOME wants to lock itself only to Linux systems with systemd, let it. It's not like there's no other desktop environments for Linux available that are init-agnostic.
November 8, 2025 at 1:34 PM
But after some thought... Dropping GNOME is probably the best choice for non-systemd distros. If GNOME wants to lock itself only to Linux systems with systemd, let it. It's not like there's no other desktop environments for Linux available that are init-agnostic.
1. Maintain an old version of GNOME that relies less on systemd and backport features.
2. Create a hard fork and innovate from there.
3. Use a highly specialized container engine to run a stripped down systemd and GNOME.
2. Create a hard fork and innovate from there.
3. Use a highly specialized container engine to run a stripped down systemd and GNOME.
November 8, 2025 at 1:34 PM
1. Maintain an old version of GNOME that relies less on systemd and backport features.
2. Create a hard fork and innovate from there.
3. Use a highly specialized container engine to run a stripped down systemd and GNOME.
2. Create a hard fork and innovate from there.
3. Use a highly specialized container engine to run a stripped down systemd and GNOME.
When they inevitably make a change that makes no sense except to push people towards systemd and GNOME, I'll do what Lennart Poettering does when he encounters a standard he doesn't like: I'll ignore it.
November 7, 2025 at 10:44 PM
When they inevitably make a change that makes no sense except to push people towards systemd and GNOME, I'll do what Lennart Poettering does when he encounters a standard he doesn't like: I'll ignore it.