From owner-freebsd-current Mon Sep 11 22:02:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA21261 for current-outgoing; Mon, 11 Sep 1995 22:02:25 -0700 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA21255 for ; Mon, 11 Sep 1995 22:02:24 -0700 Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.12/8.6.12) with SMTP id WAA12444; Mon, 11 Sep 1995 22:01:48 -0700 Message-Id: <199509120501.WAA12444@precipice.shockwave.com> To: current@freebsd.org cc: Bill Fenner Subject: Re: userconfig doesn't work on tvi925 In-reply-to: Your message of "Mon, 11 Sep 1995 18:03:22 PDT." <95Sep11.180329pdt.177475@crevenia.parc.xerox.com> Date: Mon, 11 Sep 1995 22:01:47 -0700 From: Paul Traina Sender: current-owner@freebsd.org Precedence: bulk Jordan, I was speaking with a friend about the new userconfig stuff today, and he had what I think is a simply grand idea. I am really concerned that this crap is in the kernel. I don't think it belongs there, but I was convinced by the old "dumb terminal" userconfig that it was good. Here is my suggestion. Pull out the new userconfig ENTIRELY. Get rid of it. Instead, add a sysctl interface and a staticly linked program in /sbin to operate that interface. This keeps the kernel clean, and gives you access to fancy stuff in user mode. If you want to have the old userconfig for emergencies, I have absolutely no objection to that (it would be nice if it was #ifdef'ed). Yes, I'm sorry, I realize it's a pain in the ass to throw away work, but we're really better off with a separation between kernel and user mode stuff. (hell, then you can use curses if you want). Paul From: Bill Fenner Subject: userconfig doesn't work on tvi925 Hi, I have a headless PC with a tvi925 clone as its console. The new userconfig assumes a vt100, so it is completely useless in this situation. Is there any chance of adding a "dumb terminal" mode and defaulting to it if you are on a serial console? (With, of course, a command in "dumb" mode that can switch you to full screen mode?) Bill