HAMMER is progressing very well with only 3-4 big-ticket items left to do: * On-the-fly Recovery (<--- current WIP) * Balancing * Refactoring of the spike code * Retention policy scan Everything else is now working and reasonably stable. Of the remaining items only the spike coding has any real algorithmic complexity. Recovery and balancing just require brute force and the physical record deletion the retention policy scan needs to do is already code...

Hi all, I plan to nuke awi(4), ray(4) and gx(4) before upcoming release. awi(4): 802.11 only device (DS1 and DS2, and FH). For DSSS, since it only supports DS1 and DS2, you probably won't be able to assoc 11b/g AP, which will mark DS1, DS2, CCK5.5 and CCK11 as basic rates ray(4): FH only device (is there any field FH APs nowadays?) gx(4): em(4) should be able to replace it. If you have awi(4) or ray(4), please stand up now! Best Regards, sephe -- Live Free or Die

I took the changes out, and I'm running a stock kernel, and it seems to be ok. So it's gotta be something going on. Maybe i should just use lockmgr locks, and forget the intr/serializer stuff? --Peter