warning of pending commit attempt.
peterjeremy at optushome.com.au
Tue Feb 26 19:00:11 UTC 2008
Overall, vimage sounds very useful. Are there changes to public
kernel interfaces? (ie could it potentially be MFCd)
On Mon, Feb 25, 2008 at 09:31:40PM -0800, Julian Elischer wrote:
>>> The current version referred to in the code is implemented in
>>> a manner that allows it to be COMPILED OUT.
Since even things like INET and INET6 are "compiled in" rather than
"compiled out" on request, why is vimage defaulting to "compiled in"
>No. There are some minor reorganisations of where some variables are, and
>some minor changes but they are pretty easy to confirm as being
>"functionally equivalent". Macros are used to do a lot but there are some
>places where it was not possible to hide it behind a macro, so small
>re-orgs were required.. they really are small in comparison to
>the whole work though, and as I said. quite "provable".
How much will impact on the ease with which networking stack changes
can be MFCd back to 7.x?
>I say the next few weeks because we need it to happen NOW and
>not "just before 8.0"
Agreed but I can understand Brook's reluctance to have yet another
roto-tilling of the network stack whilst there still appear to be
a few issues remaining from the last roto-tilling. IMHO, it would
be reasonable to get input from re@ as to whether they would like
the stack left alone for a while to simplify the resolution of any
issues that may crop up once 7.0 is released.
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20080226/1f30daf4/attachment.pgp
More information about the freebsd-current