Debian Developers Decide On Init System Diversity: "Proposal B" Wins

[eric457]

Wow, article's 30 minutes old, and not a single pro-systemd shill in here. Maybe they're taking christmas/new years off?
Or maybe it's because they lost? I bet it's because they lost.

yeh thats right i had same exp for mine as well.

[oiaohm]

The thing is..
The Systemd unit files are they already a script, but written in a *yet* another Script language

That the funny part Systemd unit files are technically not script language. Systemd unit files that the syntax designed not to be turing complete. The lack of turing complete cause those migrating from scripts to systemd unit files the biggest headaches.

Systemd unit files are technically "regular language", This is like regular expressions on over drive.

[tuxd3v]

systemd unit files are often supplied by upstream
rarely any systemd units in the last 5 years use shell scripts, I guess you haven't used systemd in a while.

The thing is..
The Systemd unit files are they already a script, but written in a *yet* another Script language

[ermo]

Looks to me like the Debian developers who voted considered the options carefully and decided that it was in Debian's best interests to focus on systemd (which seems to be the de facto standard system/service manager in Linux at this stage) without at the same time completely alienating people who for some reason would rather walk on hot coals than have systemd be the only init system and service manager in Debian.

To me, this also seems like the most mature choice from an interpersonal perspective.

I did do a double take when the Debian Project Leader called for compassion and respect. I can't quite decide whether I find this amusing, sad, bizarre or just -- again -- a mature reflection of the fact that dealing with and managing geeks with deeply held beliefs and values can be quite tricky if the goal is to keep said geeks happy and productive in a volunteer context.

[onicsis]

Biggest problem, things changing and coming to fast, people can't cope with this, among other things lacking of proper documentation at any level, from beginner to expert. If someone came late to the party, wondering what is happening

[OneTimeShot]

Wow - I've used both systemd and initrc extensively. They're both pretty simple to learn and use. Why do people care which one is on their box? Stuff changes, you need to stay up to date.

Also, what's all this UNIX philosophy nonsense? initrc was not part of UNIX anyway - that was inittab.

[moneyballin]

So nothing changed? The winning option is the safest one imo, that's not surprising. I honesty don't care what the solution(s) is as long as it's GPL compatible.

[carewolf]

I have no horse in this race, but it sounds to me that they took the middle path ? What am I missing ?

The second most systemd-only option on the ballot won. Basically systemd-only, but packagers are allowed to support non-systemd.

[rtfazeberdee]

Oh, it's definitely SystemD from now on. It triggers people enough to make them correct you. Thanks for the heads-up!

The rest of your post reads like that old MAD Magazine comic about why it's destined that you will win the Publisher's Clearing House Sweepstakes, because every calamity will happen to everyone that isn't you. But instead it's about how Devuan will lose because init is just so damned tricky, that you can't just make a text file called /linuxrc to replace it. No sir, only rocket surgeons should dare touch PID1. Plus, there are only four active Debian-derivatives that will do much of the lifting for them. I hope you understand if I treat your post with the appropriate TL;DR.

And you're the only person in the thread worth responding to. Consider that a relative compliment. Happy Holidays!

aawww.. bless... we've got a 12 year old posting.....

[oiaohm]

So, approximately 72 hours after the article posted, and a pro-systemd comment ends the thread again. At what point does it become mathematically impossible to be organic?

I will give you something nicely not pro systemd. Do you know how people pull out that systemd is not unix design philosophy.

https://en.wikipedia.org/wiki/Plan_9_from_Bell_Labs

Lets bring up a fun point of history. Those who write Unix and basically what is the foundation of what we call Posix standards wrote plan 9 and did the first release in 1992. Because they worked out they has massively screwed up implementing Unix.

Everything is a file design idea of Unix was not obeyed in the implementation of resource control, Process ids, User ids, Group ids... and the list goes on. Turns out these are all the points of Unix and Unix like implementations that screw up badly.

The fact sysvinit is using process id numbers means it not unix design philosophy either.

Here is a really good impossible request at the moment find me 1 init/service management solution that in fact obeys "Everything is a file" as required by unix design philosophy. I will not even restrict you to Linux. I will only put the stuff in plan 9 off limits.

So funny enough the only thing from kernel up that is to Unix design philosophy is plan 9.

We really do need to bring the Linux kernel in line with the Unix design philosophy instead of in line with Posix what is a formalisation of how Unix design philosophy was badly implemented.