native: add -t <port> option to native again

[cgundogan]

This PR brings back the option to set a port and daemonize native in order to use it with desvirt or netcat.
Can be tested with ./bin/native/gnrc_networking -t 12107 and then nc localhost 12107.

@emmanuelsearch @thomaseichinger can anyone of you test this on OS X?

[kaspar030]

This shouldn't be part of riot.

[OlegHahm]

This shouldn't be part of riot.

What and why not?

[kaspar030]

Sorry, let me rephrase. IMHO this should not be in the RIOT native port, but be provided by a small external tool.

[miri64]

So instead of putting stdio through something else than stdio (sockets in this case) we should parse stdio and provide (e.g.) UART-like behavior through an external tool?!?

[kaspar030]

No. RIOT native already has in-RIOT stdio <-> linux stdio. Adding support to pipe all that through a socket can of course be done within RIOT, but it adds a lot of unnecessary complexity. I'd rather see a small tool that does the job from the outside.

Maybe we can even reuse something existing, e.g., socat EXEC:bin/native/default.elf,end-close,stderr,pty TCP-L:8888,reuseaddr,fork.

[cgundogan]

+1 for the socat idea. Maybe it's really the better route to go with external tools here?

[OlegHahm]

👍

[cgundogan]

I just tested quickly with socat and one thing I noticed is that the pipe breaks when I attach/detach several times from that running instance. We need to cleverly bypass this somehow

[kaspar030]

@cgundogan How do you test that?

[cgundogan]

@kaspar030 can you have a look at des-testbed/desvirt#17 ? Is this what you had in mind?

[LudwigKnuepfer]

I have no particular opinion on the topic.

[kaspar030]

I'll close this in favour of des-testbed/desvirt#17.