[ On Thursday, May 4, 2000 at 07:58:08 (+0200), Dr. Rene Hexel wrote: ]
> Subject: Re: Posible virc(8) implementation
>

I still don't see why people don't just give up on this virc sillyness
and just do "vi /etc/rc.conf.d/*" and be done with it....  ;-)

>   Why not have virc create a 'virtual' rc.conf (i.e., some mkstemp()
> filename) that can be edited and then is re-distributed into rc.conf.d/
> ?  This way, chances of people using the wrong editor on the wrong
> config file are a lot smaller!

This is certainly what I expected such a command to do.  I don't know
what prompted the other convoluted and error-prone idea.

>  We could even install an rc.conf file
> that says "this file is obsolete, please use virc to edit system
> configuration".

Yup.

>   The only thing I can think of, that's not handled by this method are
> additional config parameters that are contained in none of the
> rc.conf.d/* files.  However, these could easily moved to some
> rc.conf.d/config.default (or whatever) file.  IMHO this is far less
> error-prone than having an rc.conf around that duplicates all config
> variables and can be too easily changed using vi.

Agreed.

-- 
							Greg A. Woods

+1 416 218-0098      VE3TCP      <gwoods@acm.org>      <robohack!woods>
Planix, Inc. <woods@planix.com>; Secrets of the Weird <woods@weird.com>