Regret to inform you that I have learned #systemd still exists. I had managed to avoid it for a month and a half and hoped it had gone to join the great zoo of failed information technology experiments which were always a bad idea, along with the #Commodore64 and #Netware.
Regret to inform you that I have learned #systemd still exists. I had managed to avoid it for a month and a half and hoped it had gone to join the great zoo of failed information technology experiments which were always a bad idea, along with the #Commodore64 and #Netware.
How to do zero-downtime deploys using systemd.
systemd has a socket-activation feature that's associated with starting services on demand, often paired with shutting them down they are idle.
But today I confirmed they have a great value for always-on services-- zero-downtime deploys for web services!
What happens is that systemd owns the listening socket and never stops listening during the restart. Connections are queued and succeed when the service up.
How to do zero-downtime deploys using systemd.
systemd has a socket-activation feature that's associated with starting services on demand, often paired with shutting them down they are idle.
But today I confirmed they have a great value for always-on services-- zero-downtime deploys for web services!
What happens is that systemd owns the listening socket and never stops listening during the restart. Connections are queued and succeed when the service up.
A lot of the dialog around systemd and Wayland ends up with someone saying at least one of the following:
And both of these are true. Indeed, the second is a core idea of Free Software. Free Software is about empowering users so that they are not beholden to the decisions that their software vendor made and are able to make different choices.
But most people (even most programmers) can’t decide they don’t want to use Wayland or systemd and write something different. These components are large monolithic entities. Even systemd, which is made of a bunch of coopretating daemons, has so much tight coupling between them that you can’t replace one of them without reimplementing 90% of its functionality. And each of these projects is too complex for a single person to create a replacement for unless they treat it as a full-time job.
To me, that really highlights the failure of the Free Software movement. It obsessed over licenses that prevent downstream developers from taking away rights (and making it harder for end users to exercise them) while never thinking about how to design software so that exercising these rights was easy and natural.
In a real Free Software system, option 2 should be so easy that a large fraction of users do it. Systems should be easy to shape around users’ requirements and preferences.
@david_chisnall I agree with you on the following points:
- there are open source projects which do not prioritize good system and software architecture enough
- there are open source projects that do not prioritize (and sometimes do not care one single bit) about customer value
I do not agree on the general notion or what I understand. #systemd and #wayland are not something chosen regularly by end-users but by engineers from distributors.
@agowa338 @astraleureka snitch tagging sucks
@hipsterelectron @astraleureka
Well the WHY and WHAT FOR are kinda poorly discoverable pieces of information for things in the #systemd ecosystem. So the best thing you can do is ask the people maintaining it...
Mount Proton Drive on Linux using rclone and systemd
https://github.com/dadtronics/protondrive-linux
#HackerNews #Mount #Proton #Drive #on #Linux #using #rclone #and #systemd #Linux #ProtonDrive #rclone #systemd #cloudstorage
🎉 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 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/
