Date: Sun, 17 Jun 2001 10:41:02 -0600 From: Chris Moline <ugly-daemon@home.com> To: chat@freebsd.org Subject: Re: System Tuning/Sysadmins Message-ID: <20010617104102.A20493@h24-67-61-12.lb.shawcable.net> In-Reply-To: <15148.55623.109849.700547@guru.mired.org>; from mwm@mired.org on Sun, Jun 17, 2001 at 11:22:31AM -0500 References: <20010617063505.A29241@shell.monmouth.com> <20010617073505.B20171@h24-67-61-12.lb.shawcable.net> <20010617103922.A79022@acidpit.org> <20010617093905.A20349@h24-67-61-12.lb.shawcable.net> <15148.55623.109849.700547@guru.mired.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jun 17, 2001 at 11:22:31AM -0500, Mike Meyer wrote: > Chris Moline <ugly-daemon@home.com> types: > No, don't edit generic. Whoops, that's what I meant. > Two different answers. If /etc is wrecked, then your system didn't go > multiuser, and X is going to be unusable. That has to be fixed without > X in either way. If vi is wrecked, you use /bin/ed. If that's wrecked, > it's easier to fix than X, as all you need is that one file. If you > can't get that, you have other options, starting with sed and dd. > But to use those tools, you have to know the structure of the file > you're going to edit. Ah. > Which is the real problem with the GUIify the world approach to system > administration: the GUI hides the details about what's going on, so if > that tool isn't available, the admin has no idea how to go about > fixing things with the tools that may be available. I think this is more a problem with conventional ways of doing gui's than a problem that is inherent in gui's but I see your point. Thanks, Chris Moline To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010617104102.A20493>