Good work! Could you describe on a high level how you handle .forward and smarthost, especially regarding security? thanks simon

I personally think including pkgsrc sources in the base CD release is a waste of time. It becomes outdated so quickly that it is close to worthless. What would be worthwhile would be including it in a base DVD release (aka SOC project), along with pre-built binary packages that match the sources, plus a rc.conf-controlled cron job to keep the sources up-to-date. Distribution of such a DVD release is more problematic. I do have colo space but I had to RMA the...

I agree with this sentiment. Whatever we choose must facilitate an ability by all DragonFly developers to serve out change sets I want to huck cvsup into the dumpster. Whatever source system we use needs to have a native remote update capability... and I think all the ones we are currently contemplating already do, don't they? SVN and GIT both certainly do. -Matt Matthew Dillon <dillon@backplane.com>

Generally speaking what I am recommending is that races be allowed insofar as they don't interfere with operation, which will be in most cases. The cases where it would interfere are primarily going to be related to userland blocking conditions (e.g. read() on socket blocks waiting for incoming data/disconnect/shutdown, or write() on socket blocks waiting for buffer space to become available). These blocking conditions can be resolved by sending a synchronous messag...