I've managed Suse on a number of boxes and was able to admin everything having never even opened YaST. The config files are still there just like on any other distro and the edits work just the same. The point being that YaST is simply a tool which is an _option_ for the user to manage their system if they choose to go that route. It certainly is not a requirement and doesn't need to be used at all if you are familiar enough with Linux to opt for the more traditional command line methods.

So don't use the GUI. But even this is far from the truth since most of the changes a user would make to their base system config directory (/etc) with YaST have the paths and actual file names clearly documented alongside either the edit boxes, drop menus, input fields, or help texts. I am in no way advocating that YaST is the bees knees, but let's at least get the information being offered here to contain a little more accuracy. In this case it simply is not true that a user making sysconfig changes to their /etc directory in a YaST session would have difficulty readily seeing what files were being changed.

I'm happy to hear that . I have used suse too. And same problem is I dont know what this beautifull thing do with my system. Any body have made it for personal use?? It can come from any language programming. But it must open source, so I can learn from the source. That's benefit of open source, isn't?

I'm happy to hear that . I have used suse too. And same problem is I dont know what this beautifull thing do with my system. Any body have made it for personal use?? It can come from any language programming. But it must open source, so I can learn from the source. That's benefit of open source, isn't?