From owner-freebsd-current@FreeBSD.ORG Fri Apr 9 05:15:44 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87AB716A4CE for ; Fri, 9 Apr 2004 05:15:44 -0700 (PDT) Received: from pcwin002.win.tue.nl (pcwin002.win.tue.nl [131.155.71.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id C760F43D41 for ; Fri, 9 Apr 2004 05:15:43 -0700 (PDT) (envelope-from stijn@pcwin002.win.tue.nl) Received: from pcwin002.win.tue.nl (orb_rules@localhost [127.0.0.1]) by pcwin002.win.tue.nl (8.12.11/8.12.11) with ESMTP id i39CFg46037919; Fri, 9 Apr 2004 14:15:42 +0200 (CEST) (envelope-from stijn@pcwin002.win.tue.nl) Received: (from stijn@localhost) by pcwin002.win.tue.nl (8.12.11/8.12.11/Submit) id i39CFg8u037918; Fri, 9 Apr 2004 14:15:42 +0200 (CEST) (envelope-from stijn) Date: Fri, 9 Apr 2004 14:15:42 +0200 From: Stijn Hoop To: Atte Peltomaki Message-ID: <20040409121542.GD26247@pcwin002.win.tue.nl> References: <20040408224527.GA8299@norsu.kameli.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+QahgC5+KEYLbs62" Content-Disposition: inline In-Reply-To: <20040408224527.GA8299@norsu.kameli.org> User-Agent: Mutt/1.4.2.1i X-Bright-Idea: Let's abolish HTML mail! cc: freebsd-current@freebsd.org Subject: Re: Future of FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Apr 2004 12:15:44 -0000 --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable At the risk of feeding the troll... On Thu, Apr 08, 2004 at 10:45:27PM +0000, Atte Peltomaki wrote: > Hello FreeBSD users and developers! >=20 > As an active FreeBSD user, I'm ever so interested about the future > plans of FreeBSD and direction of developement. Many of the features > that 5.x taunts are very impressive. But as of late I have been > increasingly worried about the direction (or, lack of direction) things > have been going.=20 What lack of direction? As I see it, everything is gearing up for a great 5.3-STABLE release. > Departure of Jordan and Greg. Jordan said it's not fun anymore. Is the > strive for new features driving developers past their limits, or has jkh > simply gotten old? Also kicking out Dillon, a very talented and active > programmer, didn't look good at all, especially when it went down > completely without any explanations to userbase.=20 Why drag up old stuff like this? What does it have to do with the future of FreeBSD? > Stability of 5.x: from my point of view, the 5.x series, although > including a lot of very fancy work in many areas, is nowhere near the > reliability you'd expect from a stable FreeBSD release. Originally 5.x > was due to go stable in the beginning of summer, are there any new plans > made yet?=20 And how did you determine this reliability? Why did you even expect the same reliability from a bleeding edge release, even though it's clearly noted on every page that 5.x is known to be not as reliable as 4.x? > Feature-wise: things simply don't seem quite ready. ACPI breaks every > other box, I'm glad to hear that you sent in the reports for your 'every other box'. = Or didn't you? Seriously, I think this is unfounded FUD. Nate Lawson and many others have done magic in making ACPI just work on 90% of the hardware out there. Granted, things like suspend/resume are not there yet, but then again that's not 'breaking every other box'. And please do not drag up specific examples of 'every other box' -- you are commenting on the general state of affairs, without presenting any kind of numbers. > ULE is still not SMP aware, Giant is far from being > completely removed and so on. Yet, all these features have been > presented in the media long ago, giving the impression they would be > ready (soon).=20 Well maybe you got the wrong impression. Certainly, what's far more importa= nt is whether FreeBSD claims to have these features ready or not. It's well- known that not all of these features are as far advanced as anyone would like them to be, but then again this is Very Hard Work. I for one am excited about all the features that have been realized already. > Now, I'm not trying to pick a fight with anyone. But you are trying to spread FUD in my opinion. I'd like to counter that. = Be prepared that others will want to do the same; they may not stay civil. > I just want to talk about things with their real names. And when things > are going bad, things are going bad and calling shit on one another ain't > gonna make it one bit better. I would dearly like to hear an honest opini= on > from someone who feels he knows what he's talking about, against my feeble > knowledge over much anything. And I would really like to see FreeBSD get > a grip again, put the media behind it, see what's real and attainable > and go an' do it, and as a user I will do what I can to assist.=20 As a user the best you can do is document all your problems to the develope= rs; if you want the project to go in a certain direction, or 'finish' a particu= lar project, you'll have to step in as a developer because that's how opensource (or at least this project) works. You can't sit by the sideline and say 'hey this is going wrong' while generally waving your arms about. Hope this helps you reconsider some things, --Stijn --=20 "Harry, I'm going to let you in on a little secret. Every day, once a day, give yourself a present. Don't plan it, don't wait for it, just let it happen. Could be a new shirt at the men's store, a catnap in your office chair, or... two cups of good, hot, black coffee. Like this." -- Special Agent Dale Cooper, "Twin Peaks" --+QahgC5+KEYLbs62 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAdpPtY3r/tLQmfWcRAmO8AJ9/9PhQoxrl4LIlsUuePTBXGPW2CgCghZwM yM65a4uSVN9qK9W7iHMHXlc= =91LY -----END PGP SIGNATURE----- --+QahgC5+KEYLbs62--