From owner-freebsd-security Sun May 21 23:57:49 2000 Delivered-To: freebsd-security@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id EC50937B707 for ; Sun, 21 May 2000 23:57:46 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA56693; Sun, 21 May 2000 23:57:41 -0700 (PDT) (envelope-from dillon) Date: Sun, 21 May 2000 23:57:41 -0700 (PDT) From: Matthew Dillon Message-Id: <200005220657.XAA56693@apollo.backplane.com> To: Doug Barton Cc: Brett Glass , Warner Losh , cjclark@home.com, freebsd-security@FreeBSD.ORG Subject: Re: The procfs Hole in 2.2.8-STABLE? References: <20000521140847.G96573@cc942873-a.ewndsr1.nj.home.com> <4.3.1.2.20000521225733.048a0c40@localhost> <3928D2D5.DCA07289@gorean.org> Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I think 3.4 was our 'golden release' for the 3.x series. 3.5 is only going to have small cleanups, sort of like 2.2.8 had only small cleanups over 2.2.7. People have been MFCing bugs fixes reasonably well, but that's as far as it's going to go. Many of the new features in 4.x would simply be too difficult to backport into 3.x, and a lot of the really new stuff is being built on the older new stuff in 4.0-release. There is no chance of any of that being backported. My personal opinion is that the 4.0 release *already* exceeded 3.4 in regards to stability, and 4.x in general is far, far superior in virtually all regards. SMP, VM, NFS (my babies) are direct examples. 4.0 is the first release where you can actually *TRUST* all the memory manipulation and mapping syscalls (madvise, msync, mmap) to work properly! I expect 4.1 will be the banner distribution for us if 4.0 hasn't already stolen the thunder! 3.5 will be an afterthought at best. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message