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
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 in pine, or to
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 dotfile
Ok, I see their has been a lot of talk on if the way linuxconf does its
thing is good for debian.
first things first, a user doesn't have to use linuxconf. If a user wants
to edit the file by hand they can use the existing tools that we have. Even
those aren't perfect, if I edit my sendmail.cf
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 generator for a
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 dotfile
6 matches
Mail list logo
