From owner-freebsd-current Sun Feb 7 15:13:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02134 for freebsd-current-outgoing; Sun, 7 Feb 1999 15:13:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02126 for ; Sun, 7 Feb 1999 15:13:50 -0800 (PST) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id SAA22219; Sun, 7 Feb 1999 18:13:45 -0500 (EST) Date: Sun, 7 Feb 1999 18:13:44 -0500 (EST) From: John Fieber To: Andreas Klemm cc: current@FreeBSD.ORG Subject: Re: some woes about rc.conf.site In-Reply-To: <19990207170542.A90515@titan.klemm.gtn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 7 Feb 1999, Andreas Klemm wrote: > What do you think ? Or what are your experiences ? It has caused a lot of grief with my recent install of 3.0-19990205, but I gather I'm supposed to install something later before complaining. The main annoyance has been that running /stand/sysinstall after installation diligently clobbered settings in rc.conf.site...things like default_route, moused_enable, and network_interfaces to name a few of the more frustrating ones. Hopefully that is now fixed. As for for all the debate on the name, if it is supposed to be an untouchable file, the name of rc.conf has GOT to change. rc.defaults, rc.conf.defaults, rc.param or some such, with rc.conf being the one you normally edit and rc.conf.local being sourced for people who need it for some reason. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message