From owner-freebsd-arch Sun Jun 16 14:40:13 2002 Delivered-To: freebsd-arch@freebsd.org Received: from nothing-going-on.demon.co.uk (pc-62-31-42-140-hy.blueyonder.co.uk [62.31.42.140]) by hub.freebsd.org (Postfix) with ESMTP id DE05837B423; Sun, 16 Jun 2002 14:39:55 -0700 (PDT) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.3/8.11.3) id g5GLeHa53451; Sun, 16 Jun 2002 22:40:17 +0100 (BST) (envelope-from nik) Date: Sun, 16 Jun 2002 22:40:17 +0100 From: Nik Clayton To: Julian Elischer Cc: Gordon Tetlow , Doug Barton , Nik Clayton , Brian Somers , arch@FreeBSD.org Subject: Re: 4.x compatibilty.. Was: MFC of rcNG? Message-ID: <20020616224017.A52976@canyon.nothing-going-on.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="VbJkn9YxBvnuCH5J" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from julian@elischer.org on Sun, Jun 16, 2002 at 01:24:46PM -0700 Organization: FreeBSD Project Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Julian, On Sun, Jun 16, 2002 at 01:24:46PM -0700, Julian Elischer wrote: > The reason for having 4.x branch is for 'backwards compaitible' changes > to be made available to users of 4.x FreeBSD. >=20 > The only features fo rcNG that can be MFC'd are those that are pure > additions.=20 Not to pick on you specifically, but have people forgotten how to read? In my original message I explicitly said: I realise it's quite a fundamental change to the startup system, but if it made it in to 4.7 as an alternative (so the default remains the same) . . . In other words, all these people with mission critical systems running stable see zero change. It would only be those of who did the equivalent of rcng_enable=3D"YES" (or whatever the variable is) that would get the new functionality. Giving us the chance to try it out, and test it in production environments, without needing to learn another way of doing things as part of the 'cut over to 5.x' process. Hmm. When is the existing /etc/rc* system going to be officially deprecated? Has anyone thought about that? At the moment it sounds like 5.x is going to ship with the new system, and without the old one. Shouldn't we be doing something like? 4.7 -- Announce the new system, with the old system as default 5.0 -- Use the new system as default, keep the old system 6.0 -- Remove the old system I'm sure we can bike shed the version numbers at which these events happen. N --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ (__) FreeBSD Documentation Project http://www.freebsd.org/docproj/ \\\'',) \/ \= ^ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- .\._/= _) --VbJkn9YxBvnuCH5J Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9DQXBk6gHZCw343URAmHeAJ9IGW5r+gbmePd1R62/o0frxUmeBgCgk5My XvE8KHebKF/MljOKQbElJ6M= =rwPm -----END PGP SIGNATURE----- --VbJkn9YxBvnuCH5J-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message