Solved Whatever

Alternatively, most changes (like these) are MFC'ed to -STABLE after a while. It's highly likely 10-STABLE already has the fix. Updating a 10.X-RELEASE to 10-STABLE is fairly easy. The only drawback of running 10-STABLE is that you can only update it by building world, freebsd-update(8) only works on -RELEASE versions. The biggest plus side however is that you get all the nice new features and bug fixes that have been tested and approved on 11-CURRENT without the inherent instability of -CURRENT. The current 10-STABLE tree will eventually be branched off as the new 10.2-RELEASE, which should be released sometime in August.

I've been running the latest -STABLE since 3.0 and never had any real issues with it. As a matter of fact, it actually fixed a lot of issues.
 
Have you found the exact revision in -CURRENT that has this patch? There's usually a mention when it will be MFC'ed to -STABLE. If not, you could ask on the mailing lists about it.
 
I can ask on the mailing list, but frankly I don't know the first thing about any kernel level code of FreeBSD. Furthermore, looking at the release notes for 11-CURRENT, it does not say when this NIC version, the Centrino 6325, was committed to the kernel. So I'm not really understanding what I should be doing - I rely on FreeBSD to the point that staying on 11-CURRENT is impractical as all hell, and I need wireless, obviously. I have read online about a patch floating around for 10.1-RELEASE, but I can't find the patch in question.
 
You must log in or register to reply here.
Back
Top