Posted by: David Breakey
on February 12, 2005 01:04 AM
I switched away from SuSE precisely because of YAST. Granted, this was back with SuSE 7.1, and I understand that YAST has improved dramatically since then, but I am now too familiar and entrenched with Mandrake to be willing to change (again…).
While YAST proved to be an excellent centralized administration tool, I found it supremely irritating that it would blithely erase any specific customizations that I had made directly to various configuration files, in favor of the configuration that it was aware of. At the very least, in my opinion, it should have put up a dialog warning me that it was about to do this, and "…do I want it to continue?". I've heard that current iterations of YAST do not do this anymore (and some I've talked to seem to believe that it never did—maybe I had a faulty installation, somehow?).
Don't get me wrong; there was a great deal about SuSE that I liked, and thought was very well put together, but at the time, Mandrake was just a better fit for what I needed—ok, wanted to be able to do.
Incidentally, the Mandrake configuration tools proved to be just as guilty of overwriting specific customizations as YAST was, but with Mandrake, I was able to figure out exactly how to modify the source files it used to manage these configurations; with SuSE, it just never quite clicked. Of course, that probably says more about me, rather than the quality of SuSE…
Incidentally, isn't it just Suse nowadays? I thought they decided to move away from the fanciful capitalization. Just wondering.
Learn about Linux
Download Linux
Get Linux help
Re:PR indeed....
Posted by: David Breakey on February 12, 2005 01:04 AMI switched away from SuSE precisely because of YAST. Granted, this was back with SuSE 7.1, and I understand that YAST has improved dramatically since then, but I am now too familiar and entrenched with Mandrake to be willing to change (again…).
While YAST proved to be an excellent centralized administration tool, I found it supremely irritating that it would blithely erase any specific customizations that I had made directly to various configuration files, in favor of the configuration that it was aware of. At the very least, in my opinion, it should have put up a dialog warning me that it was about to do this, and "…do I want it to continue?". I've heard that current iterations of YAST do not do this anymore (and some I've talked to seem to believe that it never did—maybe I had a faulty installation, somehow?).
Don't get me wrong; there was a great deal about SuSE that I liked, and thought was very well put together, but at the time, Mandrake was just a better fit for what I needed—ok, wanted to be able to do.
Incidentally, the Mandrake configuration tools proved to be just as guilty of overwriting specific customizations as YAST was, but with Mandrake, I was able to figure out exactly how to modify the source files it used to manage these configurations; with SuSE, it just never quite clicked. Of course, that probably says more about me, rather than the quality of SuSE…
Incidentally, isn't it just Suse nowadays? I thought they decided to move away from the fanciful capitalization. Just wondering.
#