Re: "cno" keyword for config(8)

[David Holland <dholland-tech%netbsd.org@localhost>]

On Sat, Aug 06, 2016 at 01:36:02PM -0400, Christos Zoulas wrote:
 > | SOunds like a good idea to me, it bugs me often that my "no xxx" stuff
 > | in config files keeps failing when someone deletes, or renames, xxx
 > | 
 > | But an alternative would be to just change "no" so that it doesn't fail
 > | when there is nothing to remove (make "no" effectively be "cno") - the
 > | effect (not having whatever it is) is achieved whether the "no" deletes
 > | it or whether it never existed in the first place.
 > 
 > Well, yes I thought about that and then to have a warning option to
 > print the ones that did not match so that we can see typos... What
 > do people prefer?

At least in principle you can warn about things that don't exist
(e.g. "no ihclpcib at ...") vs. things that exist but are already
turned off. Not sure how easy that is inside config though...

-- 
David A. Holland
dholland%netbsd.org@localhost