Heiko Helmle <heiko.helmle@head.de> 08/21/06 2:10 PM >>> Christian Boltz wrote: Hello,
Am Montag, 21. August 2006 11:11 schrieb Christoph Thiel:
to proceed with the SuSEconfig clearance initiative, let's take a look at SuSEconfig.gdm and SuSEconfig.wdm. Both of them are used to (re)generate config files, by reading some options from /etc/sysconfig/*. To get rid of those SuSEconfig scripts, their logic needs to be moved to /etc/init.d/xdm, to have it (re)generate the according config files prior to launching gdm or wdm.
Comments, criticism, better ideas?
Generating config files every time *dm is started is a bad idea IMHO.
Reason: It is done _at every boot_ instead of "sometimes" after installing packages or alike. So you will speedup SuSEconfig, but slow down booting a bit :-(
It depends. The init scripts could easily detect if the sysconfig-scripts are newer than the config files (or even md5sum them)
and regenerate them only when needed.
I think such a logic has to be inside for sure. But the bootup time should be reduced, not increased imho. What are other Distros doing? Why don't they need anything alike? What is so much more special about the SuSE way that others don't need anything alike? Is it just because of a 'lazy' coding stile for YaST? As YaST is reading / modifyng most of these files afaik. So: why not fix these tools? Cheers, Dominique --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org