![](https://seccdn.libravatar.org/avatar/76e90400bb2f4e0142b7d4f891af82ea.jpg?s=120&d=mm&r=g)
Hi, I have just installed 7.1Pro and was very surprise by the easy way it does. Almost everything work well (Athlon 750, CDR yamaha 6416, Geforce2, 128Mo, 40Go UDMA HD). I have just a question : I use to work with Slackware for several years before, So i use to modify config files with vi ....... . With Suse i try to do so, it works well too. But it seems that when i run YAST or YAST2 it starts suse.config and the files go to the default value (before i change them with vi). Is it possible to disable updating some config file in suse.config to let the user edit them as he want. Thank's for help. PS: Very good job from SUSE !!!! Auguste -----Message d'origine----- De : charlie ti [mailto:shadout@club-internet.fr] Envoyé : lundi 2 avril 2001 22:05 À : suse Objet : [SLE] gimp-1.2 and xsane Hello Is it possible to use gimp-1.2 and xsane? When i want to install gimp-1.2 i've got an error message telling me that i can't because libgimp is use by xsane. libgimp-1.1.so.24 is needed by photocd-1.12-253 libgimp-1.1.so.24 is needed by sane-1.0.2-62 libgimp-1.1.so.24 is needed by xsane-0.57-24 What's appening? Thank you Charlie Ti -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
![](https://seccdn.libravatar.org/avatar/4c27a583d12246b34aec3874e75c9ee6.jpg?s=120&d=mm&r=g)
On Wed, Apr 04, 2001 at 09:37:29AM +0200, LOURO Auguste wrote:
I use to work with Slackware for several years before, So i use to modify config files with vi ....... .
With Suse i try to do so, it works well too. But it seems that when i run YAST or YAST2 it starts suse.config and the files go to the default value (before i change them with vi).
Is it possible to disable updating some config file in suse.config to let the user edit them as he want.
Usually, YaST will notice that you have changed a file, and leave it alone. If that is not the case, then you can tell YaST not to touch certain files. There are several variables that you can edit in rc.config. - v -- Victor R. Cardona vcardona@home.com "Behold the keyboard of Kahless, the greatest Klingon code warrior that ever lived!"
participants (2)
-
LOURO Auguste
-
Victor R. Cardona