conf/60792: rc.conf fails to flag unknown values as error

[Ceri Davies]

The following reply was made to PR conf/60792; it has been noted by GNATS.

From: Ceri Davies <ceri at FreeBSD.org>
To: fbsd_user <fbsd_user at a1poweruser.com>
Cc: FreeBSD Gnats Submit <freebsd-gnats-submit at FreeBSD.org>,
	billf at freebsd.org
Subject: Re: conf/60792: rc.conf fails to flag unknown values as error
Date: Thu, 1 Jan 2004 22:23:04 +0000

 On Thu, Jan 01, 2004 at 01:00:40PM -0800, fbsd_user wrote:
 > 
 >  I have written enough programs in my life time to know that what you
 >  are trying to tell me is wrong.
 >  The values are in some kind of standard table, the table is scanned
 >  looking for match.
 
 No, they aren't; they're just shell variables.
 
 >  No match issue error message.  I put vidcontrol statement in rc.conf
 >  and it was flagged as error
 >  because it was native command, so I know it can be done.
 
 "Flagged as error" by what? Example please.  I believe you are mistaken
 here.
 
 >  I want this  PR's status changed to open and passed on to the people
 >  reasonable for the rc.conf code.
 >  This area of code has just been reworked in 5.2 so it's fresh in
 >  their minds.
 
 It's not a good idea.  People should be able to add their own variables
 to rc.conf, as billf has stated.  rc.conf.local is deprecated in favour
 of rc.conf, and therefore, you are in the wrong.
 
 >  Lets point this problem out to the real people who are in the
 >  position to fix it.
 
 The way this works is that if you want something that nobody else can
 see value in (or are telling you that it's a bad idea) is to implement
 it, then send the patches for review.  "I want a broken system" is not
 worthy of a PR.
 
 >  it's not your call to make. You are just front door admin person.
 
 We don't have any "front door admin" people.  You clearly don't
 understand the process here.
 
 Ceri
 
 --