From: Robert Scheck (scheck_at_etes.de)
Date: Wed Dec 05 2007 - 00:16:23 CET
Date: Wed, 5 Dec 2007 00:16:23 +0100 From: Robert Scheck <scheck@etes.de> Message-ID: <20071204231623.GA25677@intranet.hq.stgt.etes.de> Subject: Re: [suse-sles-e] (off. Should we move it out of the list?) Re: [suse-sles-e] Some questions about recntly released SLES Real time
On Tue, 04 Dec 2007, Joseph Marton wrote:
> Ah, then it's changed from the older version I used to use. Still,
> the fact that the tools are all spread all over the place are
> annoying. Trying to figure out which specific tool to run is such a
> PITA.
The Fedora/RHEL admin tools (redhat-config-* or later system-config-*)
ALWAYS had TUI and GUI, some also have/had CLI. What ever you used, you
either didn't look to it or your look was too short to say anything real
about it. Well, finally it is a matter of taste. The commands are just
always named system-config-* there and everything is in :)
Why do you have to figure out, which tool has to run? If you want to
install software, use system-config-software, in YaST you are selecting
"Install/remove Software" or however it is currently named. You would like
to configure the keyboard language layout? system-config-keyboard. Okay,
you've to think just a tiny bit, but aren't we old enough to think? ;-)
> With SLES you just fire up YaST and everything is in there.
Ever looked behind the doors? AFAIK YaST uses (or at least used) a bunch of
config files to hold variables which SuSEconfig takes to fill templates to
end up as configuration file somewhere. Ever changed your Xorg or in former
times XFree86 configuration your self and tried SaX(2)? The system-config-*
stuff has a parser to read the configuration file correctly and write it
the same syntactical way directly without walking about configuration files
holding variables for templates which will be used to generate the real
config file in the end. I may now get slapped by Novell and SuSE guys, as
YaST now also behaves same - possible and accepted. IIRC, there are still
cases, where SuSEconfig won't touch a configuration file, because you have
modified it yourself.
I don't want to blame one tool about another, both have its advantages and
both have its disadvantages and it is - as already said - also very much a
personal taste...
With kind regards
Robert Scheck
-- Robert Scheck Web: http://www.etes.de E-Mail: scheck@etes.de ETES GmbH Libanonstrasse 58 A D-70184 Stuttgart Fon: +49 (7 11) 48 90 83 - 12 Fax: +49 (7 11) 48 90 83 - 50 Registergericht: Amtsgericht Stuttgart HRB 721182 Geschäftsführende Gesellschafter: Markus Espenhain und Jan Theofel Sitz der Gesellschaft: Stuttgart USt.-Id.Nr.: DE814767446 --------------------------------------------------------------------- To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com For additional commands, e-mail: suse-sles-e-help@suse.com
This archive was generated by hypermail 2.1.7 : Tue Dec 04 2007 - 13:16:47 CET