On Tue, Jan 09, 2007 at 07:46:16PM -0500, Douglas Tutty wrote: > On Tue, Jan 09, 2007 at 07:23:29PM -0500, Roberto C. Sanchez wrote: > > On Tue, Jan 09, 2007 at 07:08:58PM -0500, Douglas Tutty wrote: > > > > > > For me, if something flat out requires a GUI I go and find a different > > > way. My firewall box for example has no gui apps at all, no X files at > > > all... Its a command-line only box. > > > > > > I use su. Its only me; I'd need an exta admin person to help me setup > > > sudo :) I limit su to the group adm > > > > > Believe me, I totally understand. At home, my firewall has no GUI or > > GUI apps, other than xterm (long story). However, right now I am > > working at a place that uses Oracle (gui-only installer) and RHEL. > > Since the senior admin is RedHat-trained, as in the company sent him to > > all the RedHat classes, he believes in using all the RedHat-provided GUI > > tools. So, our servers which really don't have a good reason to run > > GUIs, do in fact run GUIs. > > > > I switched from RH to Debian for two reasons: > > The RH GUIs kept crashing > > RH compiled their then new version to need a pentium and I was > running a 486 with 16 MB ram. > > Isn't having the GUI stuff on a server inherently less secure? I do 95% > of what I want or need to with: bash, mc, pinfo, lynx, mutt, and wget. > Add vim and python and we're up to 98%. All from the command line, and > if I want all from a serial terminal. That only leaves browsing > graphic websites and watching DVDs. For development, add Fortran77. > > How do you fix a remote server with a dead network if all you know are GUIs? > Can a GUI link up over a modem? I think you're preaching to the choir there buddy :). A
Attachment:
signature.asc
Description: Digital signature