From owner-freebsd-current@FreeBSD.ORG Tue Mar 3 02:56:50 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 080269EC; Tue, 3 Mar 2015 02:56:50 +0000 (UTC) Received: from elvis.mu.org (elvis.mu.org [IPv6:2001:470:1f05:b76::196]) by mx1.freebsd.org (Postfix) with ESMTP id E4E201066; Tue, 3 Mar 2015 02:56:49 +0000 (UTC) Received: from [172.20.17.11] (unknown [12.167.51.131]) by elvis.mu.org (Postfix) with ESMTPSA id 4CC1E341F867; Mon, 2 Mar 2015 18:56:49 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: Massive libxo-zation that breaks everything From: Alfred Perlstein X-Mailer: iPhone Mail (12B440) In-Reply-To: <54F51C1C.1050609@freebsd.org> Date: Mon, 2 Mar 2015 18:56:48 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <487A99D3-8620-48D2-9342-3D36E3445FB9@mu.org> References: <54F31510.7050607@hot.ee> <54F34B6E.2040809@astrodoggroup.com> <54F35F29.4000603@astrodoggroup.com> <54F429EF.5050400@freebsd.org> <54F46536.8040607@mu.org> <54F4C03F.7030704@freebsd.org> <54F4FECB.90501@freebsd.org> <197AA5DC-0591-4F71-BF10-51A5D8104C11@mu.org> <54F5103C.4020108@freebsd.org> <54F51C1C.1050609@freebsd.org> To: Andrey Chernov Cc: Harrison Grundy , "freebsd-current@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-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: Tue, 03 Mar 2015 02:56:50 -0000 > On Mar 2, 2015, at 6:27 PM, Andrey Chernov wrote: >>=20 >>=20 >> The responsibility is on you to provide something better, both the archit= ecture AND code. So if you want it backed out, then write something better. O= therwise step back and let progress happen. >=20 > As it seems you know a lot about my responsibility and duty, I am very > surprised by your broad interests. If you let me to speak for myself a > bit, I can tell what I feel. In this particular case my responsibility > is just to give good advice at the road fork with one way leads to > obvious hell, nothing more. I already express my opinion from the > technical point of view and don't want to participate in the flame war, > so continue this thread without me, please. >=20 Other bad ideas (in the past) were support for threads, kernel threads, SMP,= etc in the project's past. So maybe trying something new might be a good id= ea. At the end of the day, if in a year we think it's really terrible then i= t can be replaced, ripped out, or better yet can be fixed. =20 What's worse than a bad idea is not moving on any ideas.=20