On Sat, 26 Apr 2003 22:36:05 -0400
Mike Grello
Here is a tip for SuSE (and increasingly most Linux distros), if I wanted Windows I would've bought Windows. If you are going to treat the user like an idiot, then (s)he should not have to have some smarts to fix what you broke.
Power went out the other day, when it returned the terminal switch was pointed to another machine. The SuSE machine noticed it did not have it's (USB) mouse, so it started up YaST, when I switched to the SuSE system, I cancelled it, because I didn't want to make any changes. Upon bootup the mouse didn't work.
I'm sorry I have to agree with you. Yast2 has become a nightmare, it used to be what made SuSE so easy. My story? I have an old laptop. SuSE 7.2 installed in less than 30 minutes. Bip,bango,done! 8.1 takes a whole day of messing around with yast2. The windows like problem with the above? 7.2 was straight forward, and allowed me to select "lcd" as my screen type "BEFORE" trying to startx during setup. On the other hand 8.1 just automatically thinks it knows how to do the right thing(like windblows); and just tries to start sax2 which then locks up the whole machine. I am mulling over methods of using suse 7.2 as my base version, then just upgrading all the libraries myself. I am sooooooo tired of going thru the yast2 menus, marking things as taboo, only to find them being reinstalled the next time I install an rpm from yast2. Just like winblows. Simplicity and direct control over parameters is what makes a good distribution, not "fully automated auto-pilot". When I read the posts about 8.2, I'm just looking for signs that yast2 is fixed and is not such a damn resource hog. By the way, what is the last release that used yast1? 7.4 or what? My rant is done. :-) -- use Perl; #powerful programmable prestidigitation