Systemd v218

#1

Post by lelf » Sun, Dec 14, 2014, 12:12 PM UTC

Systemd v218
lists.freedesktop.org

Re: Systemd v218

#2

Post by andor » Sun, Dec 14, 2014, 12:42 PM UTC

This is cool:

  * systemctl gained a new "edit" command. When used on a unit
    file this allows extending unit files with .d/ drop-in
    configuration snippets or editing the full file (after
    copying it from /usr/lib to /etc). This will invoke the
    user's editor (as configured with $EDITOR), and reload the
    modified configuration after editing.

Re: Systemd v218

#3

Post by mahouse » Sun, Dec 14, 2014, 12:55 PM UTC

Lennart, I'm still waiting for you to embed WebKit and an email client on systemd.

Re: Systemd v218

#4

Post by pianoforted » Sun, Dec 14, 2014, 12:57 PM UTC

Why should an init.d replacement have something even remotely to do with PPPoE? What ever happened to orthogonal design?

Re: Systemd v218

#5

Post by davecheney » Sun, Dec 14, 2014, 1:10 PM UTC

When will this madness stop? Will systemd not be satisfied til it has subsumed the universe into one great pid 1 singularity?

Re: Systemd v218

#6

Post by bojo » Sun, Dec 14, 2014, 1:13 PM UTC

davecheney wrote: post #5

When will this madness stop? Will systemd not be satisfied til it has subsumed the universe into one great pid 1 singularity?

systemd - the emacs of init systems.

Re: Systemd v218

#7

Post by sztanpet » Sun, Dec 14, 2014, 1:26 PM UTC

davecheney wrote: post #5

When will this madness stop? Will systemd not be satisfied til it has subsumed the universe into one great pid 1 singularity?

I think you are mistaking systemd pid1 and systemd the project, this is not in pid1 but in the networkd component.

Re: Systemd v218

#8

Post by ealexhudson » Sun, Dec 14, 2014, 1:32 PM UTC

sztanpet wrote: post #7

davecheney wrote: post #5

When will this madness stop? Will systemd not be satisfied til it has subsumed the universe into one great pid 1 singularity?

I think you are mistaking systemd pid1 and systemd the project, this is not in pid1 but in the networkd component.

And it's substantially south of 1000 lines of code. It's not a full PPP daemon, but it is enough to set up (it seems) PPPoE - useful, example, for small embedded DSL routers.

I love that people bash Lennart for code he didn't even write...

Re: Systemd v218

#9

Post by teddyh » Sun, Dec 14, 2014, 1:37 PM UTC

pianoforted wrote: post #4

Why should an init.d replacement have something even remotely to do with PPPoE? What ever happened to orthogonal design?

There are legitimate reasons for moving the functionality of an external program into a library and using the library directly. Unfortunately, the reason for a PPoE library is not given. If I had to guess, it probably has something to do with running on an embedded platform. Or, possibly, the normal pppd binary requires too much of an operating system than systemd can provide at the point where networking needs to be set up.

These are my guesses. Your guess seem to be that Lennart is unaware or unwilling to consider orthogonal design?

Re: Systemd v218

#10

Post by qznc » Sun, Dec 14, 2014, 1:58 PM UTC

sztanpet wrote: post #7

davecheney wrote: post #5

When will this madness stop? Will systemd not be satisfied til it has subsumed the universe into one great pid 1 singularity?

I think you are mistaking systemd pid1 and systemd the project, this is not in pid1 but in the networkd component.

Maybe systemd as a project should try a rebranding campaign. The init daemon is only one of its many tools now.