Ubuntu Domain Server

Joseph Miller josephcmiller2 at gmail.com
Fri Nov 20 14:13:05 UTC 2009

> In this case, the GUI isn't well thought. For one, a GUI can have
> instructions in form of context sensitive messages. For two, with a GUI it's
> much easier to fit checks in which prevents users from shooting into their
> foot.

I disagree.  A sysadmin who doesn't understand the concepts of networking
and the underlying technoligies at stake for the services that are being run
won't be any better equipped with a GUI.  There is no shortcut to
education.  For example, if a sysadmin wants to run a DNS server but doesn't
understand the difference between a CNAME, A, and MX record - it won't
matter if you have the most well thought out GUI imaginable.  Until the
sysadmin is educated, they won't know what to do.  Now some GUI's do provide
on-screen instructions and education.  But I've also found most Linux
configuration files to include a lot of documentation as comments, many
times a lot more thorough than one could fit on a GUI for lack of screen
real estate.

> Mac OS X Client & Server is pretty good here. The flexibility is limited,
> but if you do things the predefined way you can be pretty sure not to open
> up a disaster.

The start of this conversation was aimed at an overall GUI to administer
everything to make things easier.  If the flexibility is limited, then it is
limited to its audience anyways.  The right tool for the right job. Some
people don't need much flexibility, but flexibility is critical for medium
to large IT situations.  Flexibility can still be gained from a GUI, but
requires a much more complex GUI, more complex settings, and still sysadmin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-devel-discuss/attachments/20091120/7668fa61/attachment.html>

More information about the Ubuntu-devel-discuss mailing list