Date: Wed, 2 Aug 2006 10:25:05 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Daniel Eischen <deischen@freebsd.org> Cc: freebsd-current@freebsd.org, Andrew Thompson <thompsa@freebsd.org>, "Matthew D. Fuller" <fullermd@over-yonder.net> Subject: Re: Where is thr_getscheduler Message-ID: <20060802172505.GA1935@troutmask.apl.washington.edu> In-Reply-To: <Pine.GSO.4.64.0608021303120.7796@sea.ntplx.net> References: <20060801204501.GA19647@troutmask.apl.washington.edu> <Pine.GSO.4.64.0608011657040.1810@sea.ntplx.net> <20060801211657.GA29737@troutmask.apl.washington.edu> <20060801212742.GB13841@heff.fud.org.nz> <20060801213803.GB9583@troutmask.apl.washington.edu> <20060802144255.GU69505@over-yonder.net> <20060802165604.GA970@troutmask.apl.washington.edu> <Pine.GSO.4.64.0608021303120.7796@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 02, 2006 at 01:09:21PM -0400, Daniel Eischen wrote: > > This is -current, so expect some problems like this. I do expect problems with -current such as the soisdisconnected() panic I had last night. Spent a portion of my morning preparing a bug report complete with kgdb output. Fortunately, rwatson appears to have already fixed the problem. Almost everything on a FreeBSD system depends on libc. Bumping its version number without careful coordination of bumping all other version numbers is full of landmines. Falling back of the retort "this is -current expect problesm" just glosses over what appears to be sloppy planning. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060802172505.GA1935>