To view parent comment, click here.
To read all comments associated with this story, please click here.
somebody have begining to port yast to fedora
http://mzugec.blogspot.com/2008/05/research-of-possibility-running-...
more work... and fedora could use it
mandriva have something similar to yast and it work under console to
In response to "IMO SUSE has the most complete set of configuration tools of any distro, nothing else come close - and it often works without any problems. However, if you need to make changes outside of YaST or use certain non-SUSE packages (e.g. server software that interacts with other software configured by YaST), you would be well advised not to - unless you REALLY know what you are doing (i.e. are prepared to find and read documentation, config. files and even the occasional PERL script)."
Mandriva has rpmdrake. It is not even fair to compare rpmdrake with yast. Rpmdrake is 100+ times faster and more reliable than yast. The only downside of rpmdrake (compared to yast) is that you are not patent protected so Microsoft could sue you anytime they like.
Edited 2008-06-17 13:02 UTC







Member since:
2007-08-17
Not wanting to turn this into a flame war about YaST, but...
yast is just a front end to reduce the need to use console...
you can use suse without using yast...
SuSE might be 'just a front end', however SuSEConfig (one of the main tools it is a front end to) is integral to making SUSE what it is. Yes, SuSEConfig can be disabled, but you lose a lot of what makes SUSE what it is.
Also, to say that the purpose of YaST is to 'reduce the need to use a console' completely ignores the fact that YaST is the only Linux system configuration tool which is equally usable in both a graphical and console environment (the only system configuration tool fullstop, AFAIK).
IMO SUSE has the most complete set of configuration tools of any distro, nothing else come close - and it often works without any problems. However, if you need to make changes outside of YaST or use certain non-SUSE packages (e.g. server software that interacts with other software configured by YaST), you would be well advised not to - unless you REALLY know what you are doing (i.e. are prepared to find and read documentation, config. files and even the occasional PERL script).