On Mon, Jun 02, 2008 at 10:01:28AM -0400, James Carlson wrote: > Nicolas Williams writes: > > On Fri, May 30, 2008 at 05:37:14PM -0400, Sebastien Roy wrote: > > > How does the daemon decide whether to open DLPI devices out of /dev/net > > > on some versions of Solaris, but out of /dev on others? > > > > And wouldn't it be easier to contribute libdlpi to quagga.net rather > > than avoid its use? > > I don't think it would. We'd end up with multiple versions of that > library delivered (one through quagga.net and the other through ON), > and all the problems that causes. We'd be hard-pressed to keep the > forked sources in sync, and make sure the right thing happens on each > platform.
That's not what I meant. The libdlpi contributed to Quagga would get built only when it doesn't exist on the build (target) system. Thus there wouldn't be two versions of libdlpi being delivered on any version of Solaris. > All of the DLPI code in Quagga, including the special code for > filtering out ISO packets and glue into the Quagga data structures, > amounts to 600 lines of code and comments. And other than (perhaps) > the debatable path issue, it's all based on stable interfaces. See, I'd no idea. I was expecting much worse and hoping that you could improve the DLPI code in Quagga by using libdlpi and contributing a copy so that Quagga can build on versions of Solaris that lack libdlpi (see above). Nico --
