From owner-cvs-all Wed Aug 15 9:16: 2 2001 Delivered-To: cvs-all@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 0D64637B42C; Wed, 15 Aug 2001 09:15:49 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@[147.11.46.201]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id JAA19908; Wed, 15 Aug 2001 09:15:39 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010815133221.7EB87529@hcswork.hcs.de> Date: Wed, 15 Aug 2001 09:15:44 -0700 (PDT) From: John Baldwin To: (Hellmuth Michaelis) Subject: Re: cvs commit: src/etc/defaults rc.conf Cc: cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org, Sheldon Hearn , re@FreeBSD.org Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 15-Aug-01 Hellmuth Michaelis wrote: > From the keyboard of Sheldon Hearn: > >> > The correct way to handle this would be to add support for ispppcontrol >> > to /etc/rc.network but IMHO we are too close to a release so i will not >> > touch /etc/rc.network anymore. >> >> Well the MFC is going to cause trouble for people. So either you need >> to back out the MFC or do something sensible with existing >> configurations. > > This is a reasonable opinion, but not my opinion. My opinion can be read in > the paragraph above and is based on the reaction of real i4b users, talking > to the sppp developer and a null-reaction to a post to -stable (as suggested > by Murray) on the subject. We aren't supposed to break -stable API's and what not. The MFC should have included _all_ of the needed changes. This should really be fixed before the release one way or another. > Anyway, if the release engineer allows me to integrate support for > ispppcontrol into rc.network at this point in time, i'll be happy to do it. > > Backing out the whole i4b MFC because of this is - sorry - nonsense. Backing out changes in -stable because an API or user interface is broken is nonsense? That's one of the main characteristics of -stable: not just stability as far as not crashing, but stability in APIs and user interfaces. You can add new APIs, but you shouldn't break old ones. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message