you should have told this Steven Jobs, possible you would have become famous.
but now we have to live with things like this, http://en.wikipedia.org/wiki/Launchd (at least someone with a X7 in the name, I use no apples :-), just because not everyone has such a superior knowledge like you.

ps: first post on page 100!

Which projects and what benefit? I could understand, what seems to me, the useless complication, rigidity, intrusiveness and obfuscation if there were some benefit. Your earlier post implied that the benefits of using systemd would take some time to be realized.
So, what projects and what benefit that couldnt be had otherwise with the current init?
If there were some kind of quid pro quo or net gain, i could understand the switch, but from what i have seen on various forums its causing more pain than gain.

just because OSX does it, doesn't mean it's any good

it has nothing to do with me, it has with oldschool UNIX neckbeards
today it's just copy pasta "features" marketing


for the Red Queen !
the queen of queens
may she abolish all that are different

Did someone test systemd w/o pam. Developers state that pam is optional. I only built and briefly tested systemd on a pamified Slackware. I wonder if systemd-logind really works w/o pam_systemd.so. I doubt any of the systemd developers ever used a system w/o pam.


Cheers

yes this is possible and works.
I have tested this

for gnome I have decided to build systemd with pam for session management as it will be required most likely (if not already) by wayland.

2 members found this post helpful.

Congratulations! You've won a life-size Lennart Poettering blow-up doll! All you need to do now is email him and ask for it.

2 members found this post helpful.

Good to know. Thanks


Cheers

Useless for you maybe, but I find quite useful to turn on my xbmc/kodi from my phone without having to plug in a keyboard and activating the daemon.

Again, the api of systemd is very good, it's incredible simple for developers to write a daemon (yes, I develop for it), and it works, and I think who really knows systemd do not think the problem with it is not it's usability and it's concept of wanting to be all things.

1 members found this post helpful.

I am getting too old for speeding on a skidoo, so a heated discussion about systemd is a nice weekend entertainment.


Cheers

This thread has become part of my morning routine Looking forward to the movie. Cant wait to see the casting choices for some of the main players tobi, reaper etc

Can Jeff Bridges do an Oldham accent?

Since Poettering praises how well Windows' design is compared to the antiquated '90s design of Linux, and therefore, is trying to fix Linux by remaking it in Windows' image, the perfect person to play Poettering in the movie would be Bill Gates.

3 members found this post helpful.

We need all the pro-systemd crowd to be played by the same actor, sort of LP clones.

edit:sorry!

I never said it was a bad design all around. People need to stop trying to twist my posts to suit their own agendas. If you read my post, that was NEVER said.

What I said was allocating a system full of sockets for interprocess communications is a bad idea. There's nothing wrong with using sockets, but they should be used dynamically rather than statically to keep the shared memory usage at a minimum, and if sockets aren't required for a process, use named pipes instead to keep the resources used minimal. Sockets themselves aren't bad when used properly, but wasting resources and bloating system requirements by turning the system into an HTML server and overloading the footprint isn't the best of ideas... hence why the system resource requirements from Windows XP to Windows Vista literally exploded. Svchost pulled in more and more functionality using socket activation as well as expanded it's role in the system which not only doubled the CPU and RAM requirements of Windows, but nearly tripled to quadrupled them. Is this something that you would like to see happen across the board for GNU/Linux?