Hi Erich, > And for all your effort which point into the future here it is _WELL DONE_ ;-)
> One of my concerns in the 2.6 branch will be IPSEC, as now we need to > use the native stack. It appears that with using the native stack IPSEC > will be an application like any other, so we may have now the benefit of > using Strongswan's IKEv2 implementation :-) I'll take your word for it - I've only briefly played with IPSEC a long time ago, and I've been very happy that I could do everything I need with OpenVPN. > Anyway, I need to probably get two buidltool branches, how are you > people doing this? If you mean 2 build environments (one for Bering uClibc, one for whatever it's name will be), yes, I have two separate setups (happens automatically, since the two are stored separately in CVS). Not terribly nice if one is switching between the two (since one always has to remember to have /lib/ld-uClibc.so.0 point to the right buildenv, but other than that (and the extra space this needs), it's no big deal to me. Martin ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel