From owner-freebsd-current Sun Feb 7 12:52:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12628 for freebsd-current-outgoing; Sun, 7 Feb 1999 12:52:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles235.castles.com [208.214.165.235]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12616 for ; Sun, 7 Feb 1999 12:52:26 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA07248; Sun, 7 Feb 1999 12:48:14 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902072048.MAA07248@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andreas Klemm cc: current@FreeBSD.ORG Subject: Re: some woes about rc.conf.site In-reply-to: Your message of "Sun, 07 Feb 1999 17:05:42 +0100." <19990207170542.A90515@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Feb 1999 12:48:13 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What do you think ? Or what are your experiences ? I hate it unreservedly. If we need a source of seeded default values, we should have rc.conf.default, uncommented, read-only. rc.conf is where people expect to make their changes, and it is immensely bogus to have sysinstall creating rc.conf.site which is quietly included *after* everything in rc.conf (so that when someone changes rc.conf, the change is overridden). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message