Proposed lexer for parsing krb5.conf files

Henry B. Hotz hotz at
Wed Nov 23 17:07:34 EST 2005

On Nov 22, 2005, at 1:01 PM, krbdev-request at wrote:

> Date: Tue, 22 Nov 2005 15:19:57 -0500
> From: Sam Hartman <hartmans at MIT.EDU>
> To: Wyllys Ingersoll <Wyllys.Ingersoll at Sun.COM>
> Cc: krbdev at
> Subject: Re: Proposed lexer for parsing krb5.conf files
> Message-ID: <tsl8xvgcu4y.fsf at>
> In-Reply-To: <20051122195803.GF7275 at binky.Central.Sun.COM> (Nicolas
>  Williams's message of "Tue, 22 Nov 2005 13:58:03 -0600")
> References: <D6DE73398967E54096684518594D9931827414 at exch- 
> 	<tslr799bvs2.fsf at> <4383412C.3010107 at>
> 	<tslu0e4cvvs.fsf at>
> 	<20051122195803.GF7275 at binky.Central.Sun.COM>
> Content-Type: text/plain; charset=us-ascii
> MIME-Version: 1.0
> Precedence: list
> Message: 6
> "Nicolas" == Nicolas Williams <Nicolas.Williams at Sun.COM> writes:
>     Nicolas> Right, maintaining krb5.conf by generating it from some
>     Nicolas> other repository is a way to go, as long as nothing else
>     Nicolas> is writing to krb5.conf.
> No.  When you are designing configuration sync systems they need to
> apply deltas not rewrite configurations.
> --Sam

Second that.

I can remember SA'ing an HPUX system (I'm not picking on Sun here ;-)  
and hating it.  Everything obeyed the standard config files in /etc  
and you could change/fix things there nicely.  As soon as you used  
the GUI SA tool once though it would revert every other change you  
made and the machine would stop working.

You had to give up the help/convenience of the GUI, or you had to  
give up your accumulated experience with from other systems.  No way  
to do both.
The opinions expressed in this message are mine,
not those of Caltech, JPL, NASA, or the US Government.
Henry.B.Hotz at, or hbhotz at

More information about the krbdev mailing list