On Monday 21 August 2006 12:07, Christian Boltz wrote:

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 :-(

By using a suitable dependency-based system to invoke the file's regeneration (such as GNU make), or trivially by comparing timestamps (easy for simple cases, but make would help for anything non-trivial), it should be possible to render this slowdown almost non-existent, by only regenerating the file when it is necessary to do so (i.e. when the generated config file(s) is/are out-of-date with respect to the /etc/sysconfig "parent" file(s)).

Is there an easy way to make *dm (or the initscript) read the sysconfig file directly (without reducing speed) and then starting X with some parameters instead a config file? This would be the best solution.

I may be wrong, but I belive that the _next_ version of Xorg will support this config-file-free parameterised mode of startup. I'm not in favour of any modification to xdm to support reading alternative config file formats, since that adds more of a maintenance headache than it solves. It's important to keep the sysconfig stuff separate from the upstream sources. Propagating sysconfig variables in to the native config file format of the target software as SuSEconfig does allows SuSE's config methodology not to have an impact on the target software, but to be kept separate, which is a good thing. Switching to an "on-demand" SuSEconfig approach, whereby files are regenerated just-in-time when necessary, would seem to be a positive step. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Hello, Christian Boltz [2006-08-21]:

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 :-(

Is there an easy way to make *dm (or the initscript) read the sysconfig file directly (without reducing speed) and then starting X with some parameters instead a config file? This would be the best solution. (If there are only one or two setting left that would require to regenerate config files, you should consider dropping this sysconfig variable.)

It could be done according to a time stamp, i.e. only if the sysconfig file changed. Checking a timestamp is fast, so I don't think that the slow down of the boot process is noticable by the user. Regards, Bernhard -- Pasteurs Theorie von Bazillen ist lächerliche Fiktion. -- Pierre Pachet, Professor der Physiologie in Toulouse (1872) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org