On Sun, 25 May 1997, Mark Baker wrote: > In article <[EMAIL PROTECTED]>, > Tom Lees <[EMAIL PROTECTED]> writes: > > >> the other solution is to have a small utility that stores these values, > >> can change them and gives the values to the scripts. > > > > The third solution, which I prefer is a utility which modifies the > > variables within the scripts - it's faster, it is more "backwards > > compatible" with sysadmins from other Unices, and generally it's nicer > > (less dependant on the cfgtool at boot-time). > > And if you're not very careful it does silly things if the scripts have been > modified significantly.
So you do something like:- BLAH=something # configtool=yes Then, if someone modifies the scripts, they make sure that that particular line is still there, or remove the "configtool=yes" if they don't want it. -- Tom Lees <[EMAIL PROTECTED]> http://www.lpsg.demon.co.uk/ PGP ID 87D4D065, fingerprint 2A 66 86 9D 02 4D A6 1E B8 A2 17 9D 4F 9B 89 D6 finger [EMAIL PROTECTED] for full public key (also available on keyservers) -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
