From owner-freebsd-arch@FreeBSD.ORG Mon Apr 28 08:53:12 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1EC2E37B401 for ; Mon, 28 Apr 2003 08:53:12 -0700 (PDT) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49C2643F85 for ; Mon, 28 Apr 2003 08:53:11 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.9/8.12.6) with ESMTP id h3SFrAVI045838; Mon, 28 Apr 2003 08:53:10 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.9/8.12.6/Submit) id h3SFrA0w045837; Mon, 28 Apr 2003 08:53:10 -0700 (PDT) Date: Mon, 28 Apr 2003 08:53:10 -0700 (PDT) From: Matthew Dillon Message-Id: <200304281553.h3SFrA0w045837@apollo.backplane.com> To: Scott Long References: <20030426154030.M13476@znfgre.qbhto.arg> <3EAB12AC.8050707@btc.adaptec.com> cc: freebsd-rc@yahoogroups.com cc: freebsd-arch@freebsd.org Subject: Re: RFC: Removal of the old rc system from -current X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Apr 2003 15:53:12 -0000 :Doug, : :I totally understand and support the issues with maintenance. I do, :however, have a couple of questions: : :1. Have all ports been preened of dependence on rcOG? :2. What about 3rd party software that is not in ports? : :Would it be possible and acceptable to officially deprecate rcOG in 5.1 :and then remove it sometime in June or July? I understand that this :extends the maintenance of rcOG a tiny bit, but it will also help users :and vendors transition. Also, will any seatbelts be in place to catch :software that tries to do things the rcOG way? : :Thanks! : :Scott I think you can safely scrap rcOG in 5.x. Ports should not be touching /etc/rc* scripts at all, except perhaps /etc/rc.conf, and ports install their own startup scripts in /usr/local/etc/rc.d (which I assume is still fully supported in rcNG). Most developers are conditioned not to touch the actual rc scripts in /etc so I would expect that getting rid of rcOG in 5.x would be an almost painless affair. Focus on the things that really could cause problems, not on the things that are not likely to. -Matt