That definitely isn't true with limited RAM. YaST2 uses much more RAM/swap, even if it's running with curses.
If it runs at all, which on my firewalls, it doesn't. Listen SuSE, THIS IS A PROBLEM... People (like me) are going to stop buying the SuSE distro because of this...
Since we are all off topic anyway, whatever happened to the yast2 feature from SuSE 6.4 where you could connect your local yast2 to a remote machine? That one used to be compatible with linuxconf too. The graphics in yast2 is taking steps forward, but the functionality is working backwards. This is a real problem on the pre-packaged SuSE products such as Email Server 3 which you cannot use yast or the SuSE "special" DNS webadmin tool to properly administer the DNS server, its not linuxconf compatible and doesnt come with any compilers in order to build linuxconf from source. Big gobs of money, break the no warranty seal, no help from an "installation only" support agreement, and your stuck with sub-standard tools like yast to get the job done. Who cares if its open source or not, it should be dumped source.
Cheers, Laurie. -- --------------------------------------------------------------------- Laurie Brown laurie@brownowl.com ---------------------------------------------------------------------
-- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here