Re: Tools the Parse config files (was Re: Linuxconf)

1998-06-06 Thread Martin Schulze
On Tue, Jun 02, 1998 at 02:52:50PM +0300, Shaya Potter wrote: > For the fact that we would need to write a parser for all our conf files. I > think that might be overkill, as many of our conf files are probably just > some files with a variable or two. i.e. the structure of the config file is > c

Re: Tools the Parse config files (was Re: Linuxconf)

1998-06-03 Thread Rev. Joseph Carter
On Wed, Jun 03, 1998 at 07:43:22AM +0300, Shaya Potter wrote: > > Shaya> Also, linuxconf shouldn't be used to configure a user's > > Shaya> personal information, such as .bashrc, .pinerc, those should > > Shaya> be left to either the program itself like in pine, or to a > > Shaya> package like the

Re: Tools the Parse config files (was Re: Linuxconf)

1998-06-03 Thread Shaya Potter
At 12:46 PM 6/2/98 -0500, Manoj Srivastava wrote: >Hi, >>>"Shaya" == Shaya Potter <[EMAIL PROTECTED]> writes: > > Shaya> Also, linuxconf shouldn't be used to configure a user's > Shaya> personal information, such as .bashrc, .pinerc, those should > Shaya> be left to either the program itself like i

Re: Tools the Parse config files (was Re: Linuxconf)

1998-06-02 Thread Rev. Joseph Carter
On Tue, Jun 02, 1998 at 12:46:02PM -0500, Manoj Srivastava wrote: > Shaya> Also, linuxconf shouldn't be used to configure a user's > Shaya> personal information, such as .bashrc, .pinerc, those should > Shaya> be left to either the program itself like in pine, or to a > Shaya> package like the

Re: Tools the Parse config files (was Re: Linuxconf)

1998-06-02 Thread Manoj Srivastava
Hi, >>"Shaya" == Shaya Potter <[EMAIL PROTECTED]> writes: Shaya> Also, linuxconf shouldn't be used to configure a user's Shaya> personal information, such as .bashrc, .pinerc, those should Shaya> be left to either the program itself like in pine, or to a Shaya> package like the dotfile generat