#Tag
🎉 systemd Lands Experimental Support For musl libc - Phoronix
｢ Systemd today finally merged support for building against and using the musl libc library. This is a win for Linux distributions like postmarketOS, Alpine Linux, and others that use musl by default as their standard C library or offer it as an option. ｣
> Systemd today finally merged support for building against and using the musl libc library.
> This is a win for Linux distributions like postmarketOS, Alpine Linux, and others that use musl by default as their standard C library or offer it as an option.
No, it isn`t.
Apart from its use as a replacement for SysVinit, systemd is unnecessary.
As it has evolved, systemd is a threat to Linux distributions that value clarity and simplicity.
BTW: Binary logs? WTF?
#systemd
🎉 systemd Lands Experimental Support For musl libc - Phoronix
｢ Systemd today finally merged support for building against and using the musl libc library. This is a win for Linux distributions like postmarketOS, Alpine Linux, and others that use musl by default as their standard C library or offer it as an option. ｣
> Systemd today finally merged support for building against and using the musl libc library.
> This is a win for Linux distributions like postmarketOS, Alpine Linux, and others that use musl by default as their standard C library or offer it as an option.
No, it isn`t.
Apart from its use as a replacement for SysVinit, systemd is unnecessary.
As it has evolved, systemd is a threat to Linux distributions that value clarity and simplicity.
BTW: Binary logs? WTF?
#systemd
🎉 systemd Lands Experimental Support For musl libc - Phoronix
｢ Systemd today finally merged support for building against and using the musl libc library. This is a win for Linux distributions like postmarketOS, Alpine Linux, and others that use musl by default as their standard C library or offer it as an option. ｣
Systemd ate everything because they have developers working on it and addressing issues. And they do it all under a single flag, the project called systemd.
I don't understand the hate.
It's just software, that is pretty useful. It's useful for distros, because it's well supported and works well.
It's useful for developers because it provides quite a lot of useful and stable tools to create logging and services, that are much more flexible and stable than any home grown solution.
Is it a governance issue? You don't like who is managing the project?
I don't know.
Or is it change that you don't like?
I assure you this is a good change from whatever was there before. It's not change for the sake of change.
You think it's not perfect and it could be marginally better? You have two paths ahead: join the project and help it improve or start your own. You will soon realize that the second option is actually a LOT of work, so please respect the work of others when they deserve it.
Complaining does not help.
RE: https://mastodon.social/@nixCraft/115566280074527897
"Just" 270 MB for...an idle server?
Debian is still a great distributions but let's measure the ram consumption of a freshly installed *BSD or Illumos based server. The numbers are totally different.
In fairness, it is not "just booting". The screenshot shows exim and an unattended-upgrades script started up.
The world has still yet to shake the idea that every single server in the normal case needs a standalone, monolithic, local queue/delivery, mail system running; it seems.
I wonder why systemd-timesyncd has a larger VIRT value than anything else there.
Drawing Excalubur from the Stone // @djware
Systemd adds musl compatibility for the first time, reducing the glibc-only barrier and widening its reach across lighter Linux systems.
https://linuxiac.com/systemd-introduces-experimental-musl-support/
Systemd adds musl compatibility for the first time, reducing the glibc-only barrier and widening its reach across lighter Linux systems.
https://linuxiac.com/systemd-introduces-experimental-musl-support/
@nluug Also a shout-out to the #systemd devs for their hard work 💪 So many commands and great features, that it's a great challenge what to put into this presentation and what to leave out. Thanks 😄
Want to follow them? @pid_eins @bluca @kaysievers @daandemeyer
This is a first for me: putting actual commands on the title slide 🤯 . Really trying to push the limits of getting as much information into one slide deck.
Those attending the presentation can expect a lot of #systemd commands, silly facts, and goodies.
The slides will be available after the presentation. Want to see them? Follow me here for the announcement and for other #Linux toots.
Organizer: @nluug
Location: Utrecht, The Netherlands
Date: see image
Website: https://nluug.nl/
@stefano This is indeed a great post. Refreshing to read - the author didn't distro-bash but instead highlighted how needs were met.
I have been leaning toward #FreeBSD after 20 years on #Debian, which has a special place in my heart. However, FreeBSD's *consistency*, elegant design, and better documentation are driving factors and I just can't look away.
Over these two decades, Linux has definitely changed. It's no longer what it once was: a #Unix clone. It's evolved into its own thing. Software does that and that's OK. But a lot of the changes or "improvements" have been needlessly reinventing the wheel with a worsening user experience and convoluted results. The audio subsystems (ALSA -> PulseAudio -> Pipewire and of course the mess that is/was JACK) and #SystemD are two big examples.
On SystemD, I don't disagree that Linux needed a modern init system. SystemD is faster, but from a human perspective it's worse. I am now typing *more* characters to manage services. Is there a reason why it couldn't be designed to manage services like:
> $SERVICE start/stop/restart
Instead, we are left with:
> systemctl $SERVICE start/stop/restart
But I digress.
#TBT I fell in love with FreeBSD when I first started my Linux journey in the mid-2000s, but only dabbled in it as it was never in any production environment I managed.
I have a FreeBSD VM sitting in my lab somewhere but due to other factors rarely do I get to it. I'm thinking it's time I grab a spare laptop, load it up, and use it as a daily driver to really force myself to learn it.
RE: https://mastodon.bsd.cafe/@gumnos/115551343732704834
This is a great post.
It's not "against" something - it just explains why Tim prefers to use the BSDs.
@stefano This is indeed a great post. Refreshing to read - the author didn't distro-bash but instead highlighted how needs were met.
I have been leaning toward #FreeBSD after 20 years on #Debian, which has a special place in my heart. However, FreeBSD's *consistency*, elegant design, and better documentation are driving factors and I just can't look away.
Over these two decades, Linux has definitely changed. It's no longer what it once was: a #Unix clone. It's evolved into its own thing. Software does that and that's OK. But a lot of the changes or "improvements" have been needlessly reinventing the wheel with a worsening user experience and convoluted results. The audio subsystems (ALSA -> PulseAudio -> Pipewire and of course the mess that is/was JACK) and #SystemD are two big examples.
On SystemD, I don't disagree that Linux needed a modern init system. SystemD is faster, but from a human perspective it's worse. I am now typing *more* characters to manage services. Is there a reason why it couldn't be designed to manage services like:
> $SERVICE start/stop/restart
Instead, we are left with:
> systemctl $SERVICE start/stop/restart
But I digress.
#TBT I fell in love with FreeBSD when I first started my Linux journey in the mid-2000s, but only dabbled in it as it was never in any production environment I managed.
I have a FreeBSD VM sitting in my lab somewhere but due to other factors rarely do I get to it. I'm thinking it's time I grab a spare laptop, load it up, and use it as a daily driver to really force myself to learn it.
🎉 MX Linux 25 Officially Released with Debian 13 Base / Linuxiac
｢ the major change is that all releases now include systemd by default, although SysVinit variants of the Xfce and Fluxbox editions are still available. According to developers, this will improve compatibility and simplify future maintenance ｣
https://linuxiac.com/mx-linux-25-officially-released-with-debian-13-base/
🎉 MX Linux 25 Officially Released with Debian 13 Base / Linuxiac
｢ the major change is that all releases now include systemd by default, although SysVinit variants of the Xfce and Fluxbox editions are still available. According to developers, this will improve compatibility and simplify future maintenance ｣
https://linuxiac.com/mx-linux-25-officially-released-with-debian-13-base/
🚀 Devuan 6.0 Released For Debian 13 Without systemd - Phoronix
｢ Devuan 6.0 "Excalibur" is now available as the fork of Debian GNU/Linux without the use of systemd. Devuan 6.0 is Debian 13 but for "init freedom" lets you use either SysVinit, OpenRC, or Runit as the init system ｣
During a chat today someone mentioned that they run a DBus daemon as root because it needs access to a root owned certificate. This made me realise that we should advocate "LoadCredentials=" more and move folks to DynamicUser.
https://systemd.io/CREDENTIALS/
#systemd
🚀 Devuan 6.0 Released For Debian 13 Without systemd - Phoronix
｢ Devuan 6.0 "Excalibur" is now available as the fork of Debian GNU/Linux without the use of systemd. Devuan 6.0 is Debian 13 but for "init freedom" lets you use either SysVinit, OpenRC, or Runit as the init system ｣
We celebrate #Devuan 6 release day
Devuan 6 Excalibur Review:
https://youtu.be/k5isjbhVnaY
We celebrate #Devuan 6 release day
Devuan 6 Excalibur Review:
https://youtu.be/k5isjbhVnaY
A space for Bonfire maintainers and contributors to communicate
