[juneau-lug] SuSEConfig

From: James Zuelow <e5z8652@xxxxxxxxxx>
To: <juneau-lug@xxxxxxxxxxxxx>
Date: Sun, 17 Feb 2002 22:05:12 -0900 (AKST)
I finally figured out how to tell YaST2 not to mess with my Postfix config
files - buried several levels deep in the RC-Config editor is a switch to
turn off creating the files.  The default behavior is to re-create the
config files based on what you've told YaST2, not what is in the files.
This is great if you use YaST2 for everything, but not so hot if you're
used to just opening up a terminal and editing the files.  There is also a
switch to tell YaST2 not to mess with *any* files, but so far it hasn't
caused any problems so I just turned off the Postfix editing for now.

This seems like trouble in some situations.  I was looking through
some of the options, and saw several places where the (otherwise helpful)
descriptions of the switches and options depended on the person knowing
the layout of the text file.  For example, the description of the second
to the last option for the UPS monitor says that selecting no will disable
"the next three options" - of course, the description is referring to the
layout of the actual config file, not the next three options available on
the YaST2 layout (there is only one more option there).  ALSO, you do
not have access to all of the options available (certainly not for
Postfix) - only the options that the YaST2 designers have given
you.

Consider the time needed to open the YaST2 control center, open the
RC-Config editor, navigate the tree layout, and change available values
there - and then go back with vi and make the changes you are unable to do
in YaST2 directly.  Much easier to just make all the changes in vi and
tell YaST2 to leave the file alone.

You may have figured out that I *do not like* utilities messing with my
config files.  I strongly feel that any utility like YaST2 should leave a
hand-crafted config file alone, unless absolutely necessary (say after a
version upgrade the existing config file is incompatible with a new
format).  I had several e-mail messages just plain bounce because YaST2
"knew better" and modified my config without telling me.  That is
something that RedHat (any version) never did to me, and is a strong minus
for SuSE in my book.  I guess this is an example of the "European Model"
versus the "American Model."

Since Suse still supports Postfix and Amavis and carries the packages on
the installation CDs it still comes out ahead - but I'm not as trusting of
the administration tools as I would be on a RedHat box.

Cheers,

James

(Still trying to figure out the GMT/Local time log thing - I retro'd
Postfix back to the CD version, and that didn't fix it, so there must be
something else that was changed that is responsible.)


------------------------------------
This is the Juneau-LUG mailing list.
To unsubscribe, send an e-mail to juneau-lug-request@xxxxxxxxxxxxx with the 
word unsubscribe in the subject header.
🍪 Privacy & Transparency

[juneau-lug] SuSEConfig

Other related posts:
