To answer the original post -- I'd say anyone used to being a Linux SA under RH will make the transition to SuSE without a problem. There are differences in where things are kept - there are differences in package managers (although I've seen a few posts hinting 'yum' can be used on SuSE) - there are differences in how fast each distro makes particular things available. SUSE tends to be more 'bleeding edge' and RH tends to be more 'stable' (please - no flame wars on that - it's just my impression that RH is very focused on stability - more so than SUSE).
But since the underlying guts are Linux -- I don't see why someone familiar with one distro wouldn't be able to pick up another fairly quickly. As far as the tangents on YaST -- if all you know is the GUI and don't know the underlying commands - then you'll probably get hung up on any switch in distros.. The most flexible SA's will know what's happening underneath the covers and be able to transition to whatever front end is put in place. IMHO. Scott Rohling On Mon, Aug 25, 2008 at 6:32 PM, John Summerfield < [EMAIL PROTECTED]> wrote: > Brad Hinson wrote: > >> John Summerfield wrote: >> >>> Mark Post wrote: >>> >>> >>>> like YaST, and wish Red Hat had a similar "one place to go to" for >>>> administration functions. >>>> >>>> >>> I've been arguing that one for years, before I'd even encountered YAST. >>> >>> Brad? I reckon that some of the RH admin tools are there just so RH can >>> mark checkboxes, "Got that." >>> >>> >>> (treading carefully as to not spark YaST a holy war..) >> Red Hat evaluated YaST long ago when it was proprietary, but by the time >> it was open sourced, we had written Anaconda and decided to fully focus >> on it. Since then, we've considered some all-in-one tools like >> system-config-control: >> >> http://www.indianoss.org/modules/wfdownloads/viewcat.php?cid=10 >> >> which is a front-end to the system-config-* GUIs, but this hasn't made >> it to RHEL. >> >> I haven't used YaST much recently, but it seems like a good tool. But >> we don't want to just add a YaST clone to RHEL (YaYaST?) :) Instead, >> we're focusing on our current system-config tools, like >> system-config-network for example, which got a huge z/Linux update for >> RHEL 5.2. >> > > It's not YAST that's important, it's the idea. Yast is much more than an > installer, and it's specially nice that if one tries to configure (say) > a web server and the needed software's not installed, it offers to > install it. > > Mandrake 7 or so had a similar idea, there was a KDE folder-like object > containing the configuration tools > > gnome-control-center, control-centre implement the same idea for GNOME > and KDE respectively, Apple's System Preferences, Windows' Control Panel > all provide a centralised set of configuration tools. > > > > > -- > > Cheers > John > > -- spambait > [EMAIL PROTECTED] [EMAIL PROTECTED] > -- Advice > http://webfoot.com/advice/email.top.php > http://www.catb.org/~esr/faqs/smart-questions.html<http://www.catb.org/%7Eesr/faqs/smart-questions.html> > http://support.microsoft.com/kb/555375 > > You cannot reply off-list:-) > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
