systemd lost the plot a long time ago.

[jandi@mastodon.social]

@distrowatch @bazkie @nazokiyoubinbou @nixCraft I've had an excellent experience with MX, which recently reinstated their classic dual-init support: https://mxlinux.org/blog/mx-25-dual-init-setup/

Now it's dual-init by default. My favorite Debian-based distro.

[hokid@mastodon.social]

@nixCraft Please, just stop using the term "Unix philosophy" as a fetish. There's a ton of great software that does not follow it, and I've seen enough failing init scripts in my life to convince me that endlessly stringing tools together with pipes is not a robust way of writing software.

[nazokiyoubinbou@urusai.social]

@jandi @distrowatch @bazkie @nixCraft I'm not sure I understand the benefit of dual init. Doesn't that mean you get the bloat and downsides of systemd while also using sysvinit for some reason? You're still going to have all the stuff that people want to avoid with systemd while it's installed and doing its thing, just with added complexity.

[r1w1s1@snac.bsd.cafe]

glad Slackware stays out of this different approaches are fine, but I still prefer simple rc scripts and small tools over one big system doing everything.

#slackware

[jandi@mastodon.social]

@nazokiyoubinbou @distrowatch @bazkie @nixCraft The distro supports both. As you can see in the linked post you can easily remove either, but you can also pick and choose at every boot, for any purpose (troubleshooting, dev, debug, etc). MX is a decidedly pro-user distro.

In the same vein, you can use flatpaks, snaps, appimages, debs, containers, whatever, if you so choose. It's quite flexible but not (IMO) overwhelming.

Still, of course, not everything for everyone, it might not be for you.

[oz1tmm@techhub.social]

@hokid @nixCraft
It would be quite fine if the software you strung together would follow the principle.

[hokid@mastodon.social]

@oz1tmm @nixCraft In my experience, all that is ever written this way is yet another static site generator nobody else can use to blog about the Unix philosophy.

[jenesuispersonne@piaille.fr]

@nixCraft but now gnome and kde enforce systemd usage..
We're fucked.

[lumiworx@mastodon.social]

@luxifer @nixCraft

Sorry, but there is no logical reason for systemd to need details that specific and precise for any purpose other than age verification.

If it were for birthday lookups for 'well wishers', it would be held in the calendar app. If it were for parental control, it would be under that heading, and only as a toggle of yes/no, on access to XYZ.

To think that it has a place in sustemd at all leads to a question of why any PPI data is necessary in ANY subsystem. It's not.

[luxifer@social.luxiferapp.com]

@lumiworx @nixCraft I didn't say systemd had to do it. But acting proactively before those dumb politicians starts banning Linux distribution that don't support is at least something. But I agree with you it has nothing to do there in the first place

[lumiworx@mastodon.social]

@luxifer @nixCraft

And if there's any doubt at all about the reasoning, read the very first entry in the now-closed and merged issue itself....

[lumiworx@mastodon.social]

@luxifer @nixCraft

I appreciate that everyone, including all of us in this thread are actively looking and thinking about where things stand at this moment.

The facts are clear enough that it was preemptive and was most certainly _not_ a requirement forced by lawsuites or legal actions.

As I've mentioned elsewhere, unjust and unfit laws are overturned often, but I'll add that capitulation is not a fitting way to deal with privacy principals and personal freedoms.

[cyberspice@oldbytes.space]

@jenesuispersonne @nixCraft xfce

[thaodan@mastodon.social]

@hokid it's not like systemd is one big blob.
That's how people argue.

[cyberspice@oldbytes.space]

@luxifer @nixCraft Why is it in systemd though. Why not a separate age daemon!

[cyberspice@oldbytes.space]

@luxifer @nixCraft Its not one or the other. Fork it, take the useful bits at the core, and throw away the bloat!

[oblomov@sociale.network]

@nixCraft corporate Linux takeover

[snosrapkungfu@mastodon.social]

@nazokiyoubinbou @bazkie @nixCraft i wonder if whatever junk theyre putting into systemd would be cut short by running the debian to ageless conversion script? i'd hope so #agelesslinux https://agelesslinux.org/

[siim@social.osur.ee]

@nixCraft There’s little wrong with openRC, I don’t get the hate. Every system I have and there’s about 30 of them, run openrc. Except one. These are hypervisors, firewall/routers, vms and servers. I put systemd on the desktop variant only because.. and there’s really no reason for it other than curiosity. My laptop runs openrc and it’s problem free.

[bazkie@beige.party]

@snosrapkungfu that's interesting! gonna give that a read later tnx