read a blog article about #systemd that talked about how it ultimately makes a lot of things possible for sysadmins that were simply not possible or too hard to accomplish on other init systems, and i think this is just another classic example of the pareto principle ("80% of the users use 20% of the product's features -- BUT that 20% is not the same for all of them")

to all the individuals, the fact that systemd does all those seemingly unnecessary things is annoying and they'd probably feel okay replicating one or two features it lacks using other means, but if you scale that up collectively, you'll end up with people whose systems are configured very differently, because they have different needs and requirements

so people whose job it is to actually support these set-ups (like redhat or distro maintainers) would much rather everyone use a single piece of software that does "too much" than have to solve a new mystery every single time

i currently run #alpinelinux, which does not use systemd, and i'm fine with it, but this is a distro that's targeted to a specific set of users, i wouldn't advise a typical gamer or creator to install it

and i think that should still remain an option, i like openrc and feel it does the things i specifically need well, and it's sad that some software now wants to specifically depend on systemd components

in an ideal world, instead of developers just announcing "$software now requires $systemd_component to work", we would have a period of discussion where the devs would ask "we need this functionality to be available to our software, please come up with an API that would allow this to happen, then write software that would make it work", and instead of a hard dependency on a single component, you would have different programs that people can pick and choose, and one of them would still probably be a systemd component

but this doesn't work in a "bazaar" model of development, where frequent releases are expected, and depending on what that functionality is needed for, you can't delay a security or accessibility improvement by a year or two!

@mms On the two #openbsd’s I use #openbox, on #alpinelinux it is the #wayland #openbox cousin #labwc. Except for a clock my desktop is empty as in no icons. Menus a mouse button away. Background color #rebeccapurple

Question for the #linux peeps around here: how hard would it be for someone to get a distro running with a presentable desktop running #wayfire?

Raspberry Pi had a x86 version, but that was back on the Debian 11 era...

It would be nice to have something like #alpinelinux with Wayfire on top, should make for a fairly small and lightweight option for older/simpler machines, no?

#ifstate 1.13.7 was released:
https://codeberg.org/liske/ifstate/releases/tag/1.13.7

(already available in @alpinelinux edge + 3.22 + 3.21 + 3.20 + 3.19 and in @m4rc3l's Nix flake https://codeberg.org/m4rc3l/ifstate.nix)

This maintenance release fixes some minor netns and routing related issues.

There is an open issue when using ifstate as a notify fifo script in keepalived: https://codeberg.org/liske/ifstate/issues/105 - when keepalived is reloaded any changes on vrrp constraint settings in ifstate may not apply.

#linuxnetworking #keepalived #AlpineLinux

yay, #Gnome works again on #AsahiLinux / #AlpineLinux ✨
looks like the software supply chain just needed a few weeks to recover :)

@jbz the direction #Alpinelinux appears to be going and some of the project's decisions are making it a little harder to love.

🐧 Wayback Hopes To Be Ready Next Year With Alpine Linux Planning To Use It By Default • Phoronix

https://www.phoronix.com/news/Wayback-2026-Plans

#alpinelinux #x11 #wayland

wayback: experimental X11 compatibility layer
"...allows for running full X desktop environments using Wayland components. It is essentially a stub compositor which provides just enough Wayland capabilities to host a rootful Xwayland server.
It is intended to eventually replace the classic X.org server in Alpine, thus reducing maintenance burden of X applications in Alpine, but a lot of work needs to be done first."

#AlpineLinux #Linux #Wayland #X11

#viernesdeescritorio #alpinelinux

Alpine + Plasma,no hay mucho que comentar,por ahora todo va perfect

This is my current gnome setup on #alpinelinux I'm quite happy with it.

@Chris1776 @vermaden This is similar for #alpinelinux (have not used that installer, but I use Alpine with zfsbootmenu).
https://github.com/psy0rz/alpinebox

Chimera Linux has been using apk 3 for a long time. That's helped expose a few bugs, so hopefully the Alpine switch is smooth.

https://fosstodon.org/@ncopa/114778452278033501 #AlpineLinux #ChimeraLinux

apk-tools 3 was merged to #AlpineLinux edge. Hold on to your hats!

Some of the new things are listed here:
https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/82593#note_520288

ahora andamos en alpine(dios mio quitenme el distrohopping).

voy a probarlo por 1 semana con kde plasma y contare mi experiencia sobre que tan bueno es alpine y como funciona musl para uso domestico,por ahora le hare unos pequeños ajustes a la distro y instalare las apps que nesecito por flatpak o compilandolas.

#linux #kdeplasma #alpinelinux

@dividuum Thank you for pointing me to this pull request!

#AlpineLinux is sill on kernel version 6.12.31 and so the fix is missing. 😅

I am getting tired of #popos in its current state due to some decisions around packaging, so it might be time to distro hop again.

Considering #archlinux for bare metal, #debian as a hypervisor with a new system drive, or maybe #fedora (to learn stuff) or #alpinelinux for minimalism.

Curious what people's opinions are for distros where the system layer 'just works' without locking you into a limited package registry. (Please don't recommend Ubuntu, I don't enjoy forced snapd)

#linux

I've been working with #Linux Distro package mantainers to package my software #exfetch

- Someone made an #alpinelinux package: https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/86271
- A #NixOS #nixpkg: https://github.com/NixOS/nixpkgs/pull/420636
- An #archlinux #aur package: https://aur.archlinux.org/packages/exfetch
- I've also been working on an #OpenBSD port/package on the ports@ mailing list: https://marc.info/?t=174882828000001&r=1&w=2

any other packagers for various Linux distros or *BSD systems have at it!

I'm trying to get a hyperpixel4 display working on RPi CM5 with #AlpineLinux 3.22 (or #pmos). While the console works on RPi OS it fails on Alpine - using identical config.txt tweaks. 🤔

drm_rp1_dpi and rp1_pio fails to load on Alpine. From loading with insmod it seems that rp1-pio fails due to unknown symbols.

The symbols are provided by rp1.ko - but that cannot be loaded due to "module is already loaded" (which it is not ⁉️).

Now I'm stucked an weird. Any ideas?

#AskFedi #RaspberryPi

#wayland #x11 #wm

Via: https://lobste.rs/s/qd78bl/wayback_experimental_x11_compatibility

It looks like #alpine linux are developing a wayland compositor to run a rootless #xwayland instance as means of dropping X11/Xorg as packages from their repos.

This is a crying shame for me, as I happen to use #alpinelinux on my Thinkpad.

Why they just don't use cage though, is curious to me: https://github.com/cage-kiosk/cage

But anyway, that's their choice. Good luck to them.

But one comment which came out of the lobsters post was this:

https://sourceforge.net/projects/twelveto11/

Which looks to be the promise of a wayland -> bridge, providing there's any xorg packages left in repos by then. But at least it would allow you to run waylaid-only applications on any X11 WM you wanted.

I've forked the above project here:

https://github.com/ThomasAdam/waylandx

Primarily so that I didn't have to use sourceforge, or SVN.

I'm not sure why Imake was ever used, and awk for script generation -- that's just some of the minor things which I might change, along with the portals being upgraded.

It'll be about an interesting project, and I'm just pleased someone started this, without the need for others (like myself) to have to do it from scratch.