If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Unix-like OS-es never had problem spawning many processes and socket activation doesn't belong to init. If it's so simple, reimplement it in one month or even better make it POSIX.

Wow. First systemd is bashed for being too complex, and now "UNIX" is immune to any complexity. This keeps getting better and better. What makes "UNIX" magic? Nothing. It is a now-dead 70s OS implementation(for a reason)!

One of the reasons Linux is getting its ass kicked is the abysmal kernel support for stuff that desktop user cares about; A kernel layer and init that just dont fuck up. The only way to keep it managable is keeping it fucking simple and enable a sane level of debugging. Systemd does that. There is no need to spawn shit about UNIX or POSIX compliance. users dont care.

Userland is stil uncharted land. Now Canonical starts blabbering about user session management in Upstart. Well maybe those guys should help fix the kernel layer first. THEY CHOSE NOT TO BECAUSE THEY DONT CARE. Now they want a piece of user land following their session stuff while the systemd guys have been holding back for at least 1 year because no hard systemd deps could be accepted by Canonical. Waiting one year on Canonical, and now they are on the verge to add user land deps on Upstart. How ridiculous!

Wow. First systemd is bashed for being too complex, and now "UNIX" is immune to any complexity. This keeps getting better and better. What makes "UNIX" magic? Nothing. It is a now-dead 70s OS implementation(for a reason)!

So if you put everything into one process, like COMMAND.COM, it becomes simpler?
fork() is cheap and I said unix-like, not AT&T Bell Labs UNIX.

Userland is stil uncharted land. Now Canonical starts blabbering about user session management in Upstart. Well maybe those guys should help fix the kernel layer first. THEY CHOSE NOT TO BECAUSE THEY DONT CARE.

Same as systemd does't care about POSIX.

Originally Posted by funkSTAR

Now they want a piece of user land following their session stuff while the systemd guys have been holding back for at least 1 year because no hard systemd deps could be accepted by Canonical. Waiting one year on Canonical, and now they are on the verge to add user land deps on Upstart. How ridiculous!

systemd package contains the code for many different programs (including udev). The init daemon (/usr/lib/systemd/systemd) for version 196 is 888 kB size.
...
So you see, systemd is not like COMMAND.COM

888 kb !

You're making my, and his, point for us. That is _huge_. That's 850kb of code, all unnecessary, there to increase the chance of bugs disrupting the only task init should do.

My sysvinit is ~32kb, and that is a bit too big too.

So yes, that is exactly like command.com despite systemd having some commands split off.