Forgot your password?
typodupeerror

Comment: Re:Simple set of pipelined utilties! (Score 1) 202

by drinkypoo (#47928733) Attached to: Torvalds: No Opinion On Systemd

Xorg, which on desktop is as critical as init to keep running, is not really simple.

Never go full retard. X is not even remotely as important as init. For one thing, if X dies, who will restart it? And do we really want computers that explode when the GUI dies? I, for one, would like network services to terminate gracefully. The whole idea of TCP/IP networks, the dominant network used with Unix, is peer-to-peer. I may well run both services and clients on my machine. If X dies, the clients may die (if they're not text and running in screen) but the servers won't.

kernel, which is also as critical as init to keep running, and it is *much* *much* more complex than systemd. systemd is not at the "bottom layer" of the system, there's the whole of kernel underneath still.

So the argument is that since the kernel is complex, we should add more complexity, or that more complexity won't matter? That's an ignorant, illogical argument.

And one common myth is that systemd has these so many features and systemd is pid 1 therefore pid 1 is this huge bloated monster that does udev, logging and NTP, right? Wrong; actually, just the core bits of systemd run in pid 1 and the rest is compartmentalized in a bunch of separate daemon processes.

Systemd still has to be more complicated so that it knows how to run these other processes, which wasn't even necessary. init was never meant to manage daemons. daemons were meant to manage themselves, or be run from inetd. If you want more complexity, inetd is the place to add it. And for handling daemons which don't adequately manage themselves, there's daemontools. There was simply no need whatsoever for this to happen.

So, this "increased complexity" issue is not really as bad as it sounds, realistically.

It is bad, because PID1 is now responsible for a bunch of things which could have existed in any other daemon. And rather than roll the things which actually make sense in together, everything is getting rolled together. So now not only do we depend on a complex kernel, but we depend on a needlessly complex init system. There was no good reason to put all of this stuff into the same daemon.

Comment: Re:Simple set of pipelined utilties! (Score 1) 202

by drinkypoo (#47928683) Attached to: Torvalds: No Opinion On Systemd

You can't seriously claim that systemd provides nothing that can't be done by script based init systems, shell scripts and existing daemons

Yes, yes I can. And I did.

logind is just one example

Does nothing a script can't do

But it would be an interesting project to make a Linux SysVinit distro that tried get feature parity with systemd, so that daemons could utilize the kernel "namespaces" and "capabilities"

Systemd doesn't even fucking use capabilities, just cgroups. Which we could use before systemd. Systemd manages permissions in lieu of using capabilities, e.g. apparmor or selinux.

Isn't that argument just trying to make a virtue out of the fact, that SysVinit and the like, are totally crude and primitive init systems that are unable to anything much of interest?

No. That is the virtue. They are simple. Simplicity is still a virtue.

All the analyses I have seen shows that moving crucial processes into PID2, just makes everything more fragile and opens up security holes.

Making PID1 more complex makes everything more fragile and opens up security holes.

I think that there are actually very good design reasons for why systemd is designed like it is.

NIH

It only runs one process as PID1, the daemon "systemd" which is rather small. This daemon however, is capable of "talking" with with several other processes, which gives it many advantages,

This is making init do stuff it doesn't need to do, which makes it more complex, which makes it more fragile. You should not need a detailed explanation to understand why this is a bad thing.

Comment: Re:Are you even aware of SystemD works? (Score 1) 202

by drinkypoo (#47928579) Attached to: Torvalds: No Opinion On Systemd

You don't seem to understand how SystemD actually works. The PID 1 is relatively simple -- it uses all sorts of separate (i.e. non-PID 1) helper processes to do all the heavy and complicated lifting.

Lifting which should not be done by PID 1. And PID 1 has to be more complex than it should be just to handle those external programs.

SystemD currently does a fuckton of stuff no other currently usable init system on Linux does.

It does a lot of stuff the init system shouldn't do.

(Reliable process supervision which cannot be evaded,

cgroups existed before systemd.

sane handling of process stdout/stderr

Up to the init script.

proper handling of dependencies at runtime

Already handled by several init systems.

socket activation

We call it inetd.

I don't particularly care which init system my system runs, but I want those features and currently only SystemD can deliver them.

That is ignorance at best, or perhaps a lie.

Please stop spreading FUD about things you know next to nothing about.

You have no idea about anything, that didn't stop you. I see why you didn't log in.

"Kill the Wabbit, Kill the Wabbit, Kill the Wabbit!" -- Looney Tunes, "What's Opera Doc?" (1957, Chuck Jones)

Working...