> Did these changes make it back into FreeBSD?
I'm sure that Justin's too nice a guy to say that the above question
is just about meaningless in any real-world context, so I'll jump in
and cuff you upside the head instead. :)
What Justin's describing is truly significant set of changes here, and
> Will the dedicated work of the said guru get a high priority as far as
> review and commit steps are concerned? A public semi-formal commitment
> or encouragement from FreeBSD core group may be in order to raise
> support from the community. Otherwise, folks may worry that these big
> changes, o
Julian,
Can you *please* make some attempt to pick your battles more wisely
and stop needlessly antagonizing the KAME folks? I'm sure you have
some areas of technical skill, but diplomacy is certainly not
something you excel at (in fact, you completely suck at it, let's be
honest) so perhaps you
Actually, I think quoting PR#s is a more than acceptable way of
pointing things out. They're very easy to look up for anyone (and
committers get the extra advantage of using query-pr on freefall) and
it sure beats wearing one's fingers out by entering the same
information over and over again.
We
> Something just doesn't sit well me. This shouldn't happen in a
> 100Mbit LAN. This seems like a plain vanilla network transaction, and
> FreeBSD is failing on something, where other OSes in the same
> environment don't.
You're almost certainly correct that there's a misfeature lurking in
ther
