From root@a1poweruser.com  Thu Jan  1 10:59:13 2004
Return-Path: <root@a1poweruser.com>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6C2E316A4CE
	for <FreeBSD-gnats-submit@freebsd.org>; Thu,  1 Jan 2004 10:59:13 -0800 (PST)
Received: from smtp.a1poweruser.com (oh-chardon-cmts6a-103.clvdoh.adelphia.net [67.20.101.103])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C920D43D1F
	for <FreeBSD-gnats-submit@freebsd.org>; Thu,  1 Jan 2004 10:59:12 -0800 (PST)
	(envelope-from root@a1poweruser.com)
Received: by smtp.a1poweruser.com (Postfix, from userid 0)
	id 24E0930F; Thu,  1 Jan 2004 13:59:52 -0500 (EST)
Message-Id: <20040101185952.24E0930F@smtp.a1poweruser.com>
Date: Thu,  1 Jan 2004 13:59:52 -0500 (EST)
From: fbsd_user@a1poweruser.com
Reply-To: fbsd_user@a1poweruser.com
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: rc.conf fails to flag unknown values as error 
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         60792
>Category:       conf
>Synopsis:       rc.conf fails to flag unknown values as error
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jan 01 11:00:31 PST 2004
>Closed-Date:    Thu Jan 01 11:17:58 PST 2004
>Last-Modified:  Thu Jan  1 14:30:16 PST 2004
>Originator:     Charlie &
>Release:        FreeBSD 5.2-RELEASE i386
>Organization:
>Environment:
>Description:
put kiss_my_xxxx="YES" statment in rc.conf or filewall_enable="YES"
 this is not flagged as error and should be. 
 

>How-To-Repeat:
	
>Fix:

	


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: billf 
State-Changed-When: Thu Jan 1 11:12:26 PST 2004 
State-Changed-Why:  
use -DIPFIREWALL_DEFAULT_TO_ACCEPT to compile ipfw with a 
ruleset that permits all traffic 

http://www.freebsd.org/cgi/query-pr.cgi?pr=60790 
State-Changed-From-To: open->closed 
State-Changed-By: billf 
State-Changed-When: Thu Jan 1 11:12:26 PST 2004 
State-Changed-Why:  
the fstab(5) man page is better documentation than bogus example entries 

http://www.freebsd.org/cgi/query-pr.cgi?pr=60791 
State-Changed-From-To: open->closed 
State-Changed-By: billf 
State-Changed-When: Thu Jan 1 11:12:26 PST 2004 
State-Changed-Why:  
"unknown" variables in rc.conf are not errors 

http://www.freebsd.org/cgi/query-pr.cgi?pr=60792 

From: "fbsd_user" <fbsd_user@a1poweruser.com>
To: <freebsd-gnats-submit@FreeBSD.org>
Cc:  
Subject: Re: conf/60792: rc.conf fails to flag unknown values as error
Date: Thu, 1 Jan 2004 14:48:27 -0500

 Hello that's just what I am complaining about.
 
 That should generate warning error.
 
 Are you the correct person who should be reviewing the problem
 reports
 You sound like you do not know what you are talking about.
 

From: "fbsd_user" <fbsd_user@a1poweruser.com>
To: <freebsd-gnats-submit@FreeBSD.org>
Cc:  
Subject: Re: conf/60792: rc.conf fails to flag unknown values as error
Date: Thu, 1 Jan 2004 15:45:14 -0500

 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 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.
 
 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.
 
 Lets point this problem out to the real people who are in the
 position to fix it.
 
 it's not your call to make. You are just front door admin person.
 

From: Ceri Davies <ceri@FreeBSD.org>
To: fbsd_user <fbsd_user@a1poweruser.com>
Cc: FreeBSD Gnats Submit <freebsd-gnats-submit@FreeBSD.org>,
	billf@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
 
 -- 
>Unformatted:
