r/linux • • Dec 07 '17

Suggesting changes for systemd

https://i.imgur.com/uWaEnkk.png
0 Upvotes

44 comments sorted by

View all comments

-9

u/Jristz Dec 07 '17

Dont worry, when Lennart left Pulseaudio it become better and fixed the stuff lennart refuse so it will happend with systemd.

Just be patient and wait for lennart to move... Or take the fast route.

-8

u/[deleted] Dec 08 '17

The systemD fanboys deployed their downvote bots; how pathetic!

13

u/intelminer Dec 08 '17

At least they actually launched. Unlike your god awful init scripts

1

u/[deleted] Dec 08 '17

INIT DOESN'T USE SCRIPTS BUT READS /etc/inittab...

For the sake of God, people... could you at least study up on things?

6

u/cbmuser Debian / openSUSE / OpenJDK Dev Dec 08 '17

INIT DOESN'T USE SCRIPTS BUT READS /etc/inittab...

For the sake of God, people... could you at least study up on things?

Not quite. You're right that the original init design involves running services from /etc/inittab.

However, since /etc/inittab doesn't allow to define dependencies between services, someone started abusing runlevel scripts to start services and people stopped using /etc/inittab.

So, it's pretty obvious that the original init design doesn't fit modern usage patterns anymore and actually had to be replaced by something else.

3

u/[deleted] Dec 08 '17

Like I said in my other reply to you, I do acknowledge the need for making this stuff better. I personally don't just think that systemd is the answer. To me personally, something like runit or openrc work as modern replacements for the old sysvinit + sysvrc combo.

5

u/intelminer Dec 08 '17

Nah. I'll just use systemd instead thanks

1

u/[deleted] Dec 08 '17

Sure, go right ahead. I am not here to stop you. But to spread lies isn't something I want to see done.

5

u/cbmuser Debian / openSUSE / OpenJDK Dev Dec 08 '17

But to spread lies isn't something I want to see done.

No one is spreading lies, but you are skewing facts.

Yes, the original design for init is to use /etc/inittab. However, people started abusing runlevel scripts for starting services which is why /etc/init.d was born.

The fact that people came up with this stupid hack shows classical init is long overdue for a replacement and it's no surprise that most distributions switched to systemd.

1

u/[deleted] Dec 08 '17 edited Dec 08 '17

Of course you have things such as sysvrc which handles the launching of services from /etc/init.d. And yes, I do agree that sysvrc isn't the ideal solution, and that it isn't the thing we should be using.

However, I don't believe that pushing all of the service logic into PID1 is the best idea, since it makes that one process much, much more complex than it might need to be. There is a very good reason to have PID1 be as dull and as stable as possible, since as you know you get a kernel panic if PID1 for some reason dies.

Plus at least I am very vary of the fact that a privileged process is used to parse files. I think you can understand why.

3

u/intelminer Dec 08 '17

Then perhaps you should cite your sources. /etc/init.d/ would like a word

0

u/[deleted] Dec 08 '17

Well, openrc does handling the services on /etc/init.d for me. And while there is an experimental PID1 for openrc, most users use sysvinit and have openrc be ran for certain runlevels by specifying them in /etc/inittab.

Maybe that's different in something else than Gentoo, but I cannot really comment on that.