From owner-freebsd-security@FreeBSD.ORG Mon Apr 18 01:31:05 2005 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8430516A4CE for ; Mon, 18 Apr 2005 01:31:05 +0000 (GMT) Received: from smtpq3.home.nl (smtpq3.home.nl [213.51.128.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id D586343D39 for ; Mon, 18 Apr 2005 01:31:04 +0000 (GMT) (envelope-from danny@ricin.com) Received: from [213.51.128.133] (port=54261 helo=smtp2.home.nl) by smtpq3.home.nl with esmtp (Exim 4.30) id 1DNL6N-0002U8-OI for freebsd-security@freebsd.org; Mon, 18 Apr 2005 03:31:03 +0200 Received: from cp464173-a.dbsch1.nb.home.nl ([84.27.215.228]:51094 helo=desktop.homenet) by smtp2.home.nl with esmtp (Exim 4.30) id 1DNL6M-0007MF-LX for freebsd-security@freebsd.org; Mon, 18 Apr 2005 03:31:02 +0200 From: Danny Pansters To: freebsd-security@freebsd.org Date: Mon, 18 Apr 2005 03:30:37 +0200 User-Agent: KMail/1.8 References: <20050412213328.GC1953@lava.net> <6.2.1.2.2.20050417185631.05349ee0@localhost> In-Reply-To: <6.2.1.2.2.20050417185631.05349ee0@localhost> X-Face: "0Qv=,p:+]LvuqrtS4U\z3k"qN=.1]@=?utf-8?q?=258=3F=3BPoab=23v=27F=7E=0A=09!Wm=5Fe-=24=7EL=5D=3B?=>[c*L^Qoladj)x@mH}Bqz"vLO?Zdl}[@V@=?utf-8?q?U=3Fx3=23lI=3A=0A=09=24DN=7E!Hr?=@K`-mNv"zXm MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200504180330.37184.danny@ricin.com> X-AtHome-MailScanner-Information: Please contact support@home.nl for more information X-AtHome-MailScanner: Found to be clean Subject: Re: Will 5.4 be an "Extended Life" release? X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Apr 2005 01:31:05 -0000 On Monday 18 April 2005 03:05, Brett Glass wrote: > At 03:33 PM 4/12/2005, Clifton Royston wrote: > > If 5.4 is expected to be an extended-life branch, I would consider > >moving them up to 5.4 instead, to get a leap on current technology. > >Has that decision been made yet? > > I have a similar dilemma. Currently, I am building all production > servers with 4.11. But this means that I can't take advantage of > AMD64 processors or some other things that are available in 5.x. > And 5.x does some nice things, such as sandboxing BIND by default. > Finally, it seems as if CPU manufacturers are rapidly moving toward > multiple core processors, which need sophisticated SMP to work well. > So, I'd really like to move to 5.4 when it ships. > > Trouble is, from the reports I'm seeing on the -STABLE list and > my own experiments, I don't yet know if 5.4 is going to be as > fast (especially at disk access) or stable as 4.11. (Many of the > systems I am building will need very fast disk access, because they > will be used as database servers and caches.) What's more, here we > are at RC2, and there are still a number of open issues, as shown at > > http://www.freebsd.org/releases/5.4R/todo.html > > So, I am wondering if I should stick with 4.11, favoring fast single > CPUs over multiprocessor systems, for production machines -- and then > jump to 6.0 when it's released. Will security fixes be available long > enough for me to do this if need be? Let me just boldly insert that IMHO, if 6.X is going to become stable this autumn already that indeed 5.4 or maybe 5.5 at least one of those must be long-term-supported. I'm sure one of the two will, as one of the two will reflcet ultimately the walk-of-life of 5-STABLE, won't it? FYI, as far as I have noticed 5.4 is mostly a bugfix/stabilize efford over 5.3, so yes, it should be a lot better. I'm currently testing it with a UP P4 using HTT and SMP (don't use SCHED_ULE for this ;-) and it seems to go fine. Dual/multiple core CPUs are going to be the norm. In that respect we're doing really well. I wish ULE got promoted/fixed though... Hmm, I seem to have diverged from -security but so has Brett already.. :) I think amd64 is still a bit fragile. I also am interested to see how the jump to 6-STABLE will go, but inevitably there will be some 5.X maintanance release that will go on for a long time. Does anyone really doubt that? I don't, also consider that 4.X will have to be phased out ASAP (or be prepared to support 3 system compilers, I don't think so, no one would like that for a long time). There's not much need for concern IMHO altogether. Dan