YaST - i won't even touch YaST2 here - is nice for the beginner and the person who wants to use a functional system without worrying too much. but YaST is a nightmare for the established linux expert (i am blushing just a litte - but please don't consider me arrogant). it's the windows syndrome - make administration easier at the cost of complicating things and hiding important details. for instance, configuring my PCMCIA eth0 device is not something to be done in any other location than /etc/pcmcia/network.opts. but hey, i am an established redhat/debian Linux user and new to suse, so i shall not rave and drool about things that i don't really have experience with right here. i do have a question: what if i decided to abandon YaST, to uninstall it (YaST2 is already gone anyway), to move all YaST config stuff to something like /var/adm/backup or ~root/backup, to create my own scripts, and to use suse as a linux system and not as a suse system with YaST? sure, i'd loose installation support, but i don't really want that anyway. are there other consequences? what about certifications? as i understand, suse uses LPI certs - so knowledge of YaST should not be required. am i right? is anyone of you running suse without YaST? experiences? thanks, martin [greetings from the heart of the sun]# echo madduck@!#:1:s@\@@@.net -- nobody expects the spanish inquisition.