Olivier Mueller wrote: > Le 29 nov. 06 à 01:34, Scott Long a écrit : > >> I just merged the fixes into RELENG_6 and RELENG_6_2. Thanks for >> the reminder. > > thanks, but what about RELENG_6_1? Under freebsd 6.1 it is still not > coming: > I have this in my cvsup file: *default release=cvs tag=RELENG_6_1 > > Should I rather use RELENG_6 to stay uptodate? After a cvsup now, I > get this version from 14.04.2006: > -rw-r--r-- 1 root wheel 217151 Apr 14 2006 if_bce.c > __FBSDID("$FreeBSD: src/sys/dev/bce/if_bce.c,v 1.2.4.2 2006/04/13 > 22:42:07 ps Exp $");
RELENG_6_1 is frozen and only security and errata changes are allowed under security-officer@'s permission (IIRC re@'s approval is required for errata changes). Because we are working on 6.2-RELEASE, it's likely that these changes would never get into RELENG_6_1. So, there are three options: - Manually checkout RELENG_6_2's sys/dev/bce and replace yours, compile, install a new kernel. This way would bring your bce(4) driver up-to-date, while retaining other parts untouched. For Dell [12]950 boxes, I think mfi(4) changes are also useful. - Upgrade to RELENG_6_2. This brings a lot of stability enhancements. However, if this is a production server you may want to wait for the final RELEASE. - Use RELENG_6. This is potentially somewhat risky, but newly discovered bugs are fixed in RELENG_6 and the risk is less than running a raw -CURRENT. Cheers, -- Xin LI <[EMAIL PROTECTED]> http://www.delphij.net/ FreeBSD - The Power to Serve!
signature.asc
Description: OpenPGP digital signature