GoBGP: BGP Implemented in Go

Re:GoBGP: BGP Implemented in Go by vbernat on Monday April 18, 2016 @03:49PM (#11522655)

gcc has no problem with static linking. glibc can be statically linked (with gcc or clang) except the pluggable parts, which is NSS. How would you reconcile static linking and plugins?

[ Parent | on HN ]

Re:GoBGP: BGP Implemented in Go by pjmlp on Monday April 18, 2016 @04:23PM (#11522898)

By making use of plugin selection at compile time, like we used to do when dynamic linking wasn't available in mainstream OSes.

[ Parent | on HN ]

Re:GoBGP: BGP Implemented in Go by vbernat on Tuesday April 19, 2016 @03:23AM (#11525373)

The whole idea of NSS is to be pluggable to let the local administrator chooses what they need.

[ Parent | on HN ]

Re:GoBGP: BGP Implemented in Go by pjmlp on Tuesday April 19, 2016 @03:45AM (#11525464)

Back in the day when UNIX only had static linking that type of plugability was achieved via configuration files and UNIX IPC.

Dynamic linking just makes it easy to program for the same scenario.

[ Parent | on HN ]

Re:GoBGP: BGP Implemented in Go by fpoling on Tuesday April 19, 2016 @07:35AM (#11526225)

As a result of that good intention glibc must now be compiled into each and every program that wants to allow a customization complicating life for anybody who writes system software in anything but C/C++. I would rather preferred for NSS to never happen and instead Linux defined a set of services available over unix sockets for things like DNS resolution or user/group databases.

[ Parent | on HN ]