Systemd programming part 2: activation and language issues

> incorporate the functionality of portmap/rpcbind within systemd's PID 1 itself

That's absolutely not what the author meant :
> bind an arbitrary port, register that port with rpcbind

This would be one time process for "rpc-sockets" which is really close to the already include socket activation. This could be added as an option to the current socket unit I think.