> From: "Kester Clegg" <[EMAIL PROTECTED]>
>
> I think very little, *but* it does miff me a bit when Yast overwrites
> certain files (or rather, SuSEconfig does) everytime you run it; e.g. kdmrc,
> ppp stuff... and there are many ocassions when running every update tool
> (such as those for teTeX) is irratatingly slow. However, I do like the idea
> of a central rc.config file with variables you can set which then run
> scripts as you enter a particular run level. IMHO, this is a nice feature
> once you get the hang of it.
> k.
A kludge to stop SuSEconfig trampling over your nice handcrafted suseppp
configuration files, is to rename them to something that is not in the ISP
database. So instead of generic.chat and generic.options I use dol.chat and
dol.options. Therefore SuSEconfig complains each time it runs that there is
no doldf entry, but it leaves well alone. Yes it still tampers with the
generic.* files as it sees the need, but I don't use them so I am happy.
For everything else I am glad that YaST and SuSEconfig take care of the hard
work.
BTW, I don't use kdmrc, but aren't you supposed to be able to put your
customisations in susewmrc, or something like that?
dproc
--
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html
