From owner-freebsd-current  Mon Sep 11 23:27:55 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id XAA24419
          for current-outgoing; Mon, 11 Sep 1995 23:27:55 -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 XAA24413
          for <current@freebsd.org>; Mon, 11 Sep 1995 23:27:53 -0700
Received: from localhost (localhost [127.0.0.1]) by precipice.shockwave.com (8.6.12/8.6.12) with SMTP id XAA12850; Mon, 11 Sep 1995 23:26:43 -0700
Message-Id: <199509120626.XAA12850@precipice.shockwave.com>
To: davidg@Root.COM
cc: current@freebsd.org, Bill Fenner <fenner@parc.xerox.com>
Subject: Re: userconfig doesn't work on tvi925 
In-reply-to: Your message of "Mon, 11 Sep 1995 22:14:47 PDT."
             <199509120514.WAA04710@corbin.Root.COM> 
Date: Mon, 11 Sep 1995 23:26:43 -0700
From: Paul Traina <pst@shockwave.com>
Sender: current-owner@freebsd.org
Precedence: bulk


  From: David Greenman <davidg@Root.COM>
  Subject: Re: userconfig doesn't work on tvi925 

  >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).
  
     That's all nice and fine, and we *should* write a user program to do
  configuration, but this has nothing to do with why 'userconfig' was created.
  It was created so that people could boot/install FreeBSD without having to
  rip their machine apart and reconfigure all of their hardware to conform to
  our GENERIC kernel. If you can't boot the system, then you can't run the fanc
  user program from /sbin to do the dirty deed.

I realize that.  Please re-read the fourth and fifth lines that
you quoted from me.