6 ms·

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

ealexhudson 12y ago
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...
- drdaeman 12y ago
  I'm worried about "without an external pppd daemon" part.
- drdaeman 12y ago
  I'm worried about "without an external pppd daemon" part. There's no point in PPPoE without PPP. And if they say "without external pppd" this means they're going to ship a full-fledged PPP daemon.
  - eggnet 12y ago
    The linux kernel has had native PPPoE support since 2.4. https://wiki.debian.org/PPPoE https://wiki.debian.org/PPPoE
    - drdaeman 12y ago
      Yes, that's the difference with rp-pppoe.so (using kernel module to handle encapsulation, userspace code only sets up the sockets) and pppd's pty option (got it a bit wrong in my other comment in this thread, believed it's a pipe, thanks for correcting) with separate process to do so. It doesn't really matter. More than this, Linux kernel has kernel-mode PPP. But still a few parts of PPP, and all accompanying control protocols (especially authentication-related ones like EAP - you don't want that beast in the kernel!) are done in userspace.
- TheDauthi 12y ago
  While he didn't write it, he did choose to include it. Still, as someone on the fence, I'd really rather just hear about the software itself.
qznc 12y ago
Maybe systemd as a project should try a rebranding campaign. The init daemon is only one of its many tools now.
- agumonkey 12y ago
  This still smells funny. The fact that the whole project is handle as one may make the communication between developers and also program component too easy (coupling). Personally I'm a bit overwhelmed by all the 'special strings', flags and options added at each release.
- stefantalpalaru 12y ago
  Yeah, they should call it "Linux for Workgroups".
  - panzi 12y ago
    That name is already taken: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ad81f0545ef01ea651886dddac4bef6cec930092 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.g...
    - digi_owl 12y ago
      Would not be the first time systemd has overloaded something kernel related...
digi_owl 12y ago
I have come to suspect that the systemd devs are fueling that confusion, so that debates can disintegrate into a mess of arguments over semantics.

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...

drdaeman 12y ago
I'm worried about "without an external pppd daemon" part.
drdaeman 12y ago
I'm worried about "without an external pppd daemon" part. There's no point in PPPoE without PPP. And if they say "without external pppd" this means they're going to ship a full-fledged PPP daemon.
- eggnet 12y ago
  The linux kernel has had native PPPoE support since 2.4. https://wiki.debian.org/PPPoE https://wiki.debian.org/PPPoE
  - drdaeman 12y ago
    Yes, that's the difference with rp-pppoe.so (using kernel module to handle encapsulation, userspace code only sets up the sockets) and pppd's pty option (got it a bit wrong in my other comment in this thread, believed it's a pipe, thanks for correcting) with separate process to do so. It doesn't really matter. More than this, Linux kernel has kernel-mode PPP. But still a few parts of PPP, and all accompanying control protocols (especially authentication-related ones like EAP - you don't want that beast in the kernel!) are done in userspace.
TheDauthi 12y ago
While he didn't write it, he did choose to include it. Still, as someone on the fence, I'd really rather just hear about the software itself.

qznc 12y ago

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

agumonkey 12y ago
This still smells funny. The fact that the whole project is handle as one may make the communication between developers and also program component too easy (coupling). Personally I'm a bit overwhelmed by all the 'special strings', flags and options added at each release.
stefantalpalaru 12y ago
Yeah, they should call it "Linux for Workgroups".
- panzi 12y ago
  That name is already taken: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ad81f0545ef01ea651886dddac4bef6cec930092 http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.g...
  - digi_owl 12y ago
    Would not be the first time systemd has overloaded something kernel related...

digi_owl 12y ago

I have come to suspect that the systemd devs are fueling that confusion, so that debates can disintegrate into a mess of arguments over semantics.