From owner-freebsd-current@FreeBSD.ORG Sun Jun 27 00:23:18 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 ABA1416A4CE for ; Sun, 27 Jun 2004 00:23:18 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id C3CB243D53 for ; Sun, 27 Jun 2004 00:23:17 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.11/8.12.11) with ESMTP id i5R0K6cQ037335; Sat, 26 Jun 2004 18:20:06 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 26 Jun 2004 18:20:23 -0600 (MDT) Message-Id: <20040626.182023.07659343.imp@bsdimp.com> To: phk@phk.freebsd.dk From: "M. Warner Losh" In-Reply-To: <20040626.181218.21873777.imp@bsdimp.com> References: <20040626231221.GA11573@dragon.nuxi.com> <3949.1088292437@critter.freebsd.dk> <20040626.181218.21873777.imp@bsdimp.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: HEADSUP: ibcs2 and svr4 compat headed for history 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: Sun, 27 Jun 2004 00:23:18 -0000 In message: <20040626.181218.21873777.imp@bsdimp.com> "M. Warner Losh" writes: phk> Or could it be, just by chance, that I recognized that nobody on phk> core (or the TRB) would have enough information to answer the very phk> simple question: "Is there a significant use of these bits which phk> we are currently unaware off ?", and therefore decided to poll a phk> larger audience ? imp> Polling a larger audience is a necessary step in removing the bits. imp> It may not be sufficient, however. One large user could veto this imp> removal if core@ thought it important to keep that user happy, for imp> example. I'd like to add that I doubt there is such a user. However, since members of core have replied to this thread, they are aware that it is happening and can bring it to core@ to see if core@ feels it should stop. To make it clearer, I just forwarded stuff to core@ to see if anybody has an objection there. If so, we'll let you know. Warner