Mailinglist Archive: opensuse (1239 mails)

< Previous Next >
Re: [opensuse] ssytemd and openSUSE
On 6/18/2013 1:39 PM, Anton Aylward wrote:
Carlos E. R. said the following on 06/18/2013 01:01 PM:
On Tuesday, 2013-06-18 at 12:55 -0400, Cristian Rodríguez wrote:

Sir, systemd has zero control over the how the networking tools work.


The messages I got that both nm and ifup were starting came from
systemd >:-)

And xinetd of old had zero control over how cups, rsync, vnc, ftp, ssh
and others work ...

But they are all started by the xinet daemon. The daemon was a dispatcher.

Similarly systemd serves as a dispatcher and starts up named and many
others. That's all it can do - how they work "internally" has nothing
to do with systemd.

If you have a device whose start up requires you to shove coal into the
furnace, light it and "press enter" when the steam pressure reaches
90psi then systemd has no control over the shovel or the over-pressure
escape safety valve either.

Of course some things end up being done by rules in udev.
Systemd start up the daemon for all that ... something I'm just begining
to learn about

Its a shame that USG went in a different direction from Plan9 so we
can't have network devices and names under /dev ....

Reading from /dev/ipv4/ makes so much sense ... :-)

Who knows? maybe that will be possible in the near future :-/

Don't at least ksh and bash implement that in the shell?
zsh also has a tcp module but it gives a tcp_shoot command that works like netcat not a virtual device node or file. But you're right, the shell doing it doesn't help your c/other program that would like to do it.

That said, I never do use this feature even though it's been around forever in ksh, which I have also been using forever.

To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >