From owner-freebsd-current  Mon Sep 11 22:46:04 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id WAA22856
          for current-outgoing; Mon, 11 Sep 1995 22:46:04 -0700
Received: from time.cdrom.com (time.cdrom.com [192.216.222.226])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA22850
          for <current@freebsd.org>; Mon, 11 Sep 1995 22:46:01 -0700
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id WAA01537; Mon, 11 Sep 1995 22:45:54 -0700
To: Paul Traina <pst@shockwave.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:01:47 PDT."
             <199509120501.WAA12444@precipice.shockwave.com> 
Date: Mon, 11 Sep 1995 22:45:53 -0700
Message-ID: <1535.810884753@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: current-owner@freebsd.org
Precedence: bulk

> Here is my suggestion.

It won't work.

> 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,

Not if you never GET to user mode, it doesn't!  Perhaps by
complicating the interface we've obscured the purpose somewhat, but
the primary purpose remains "getting the user installed on the hard
disk."

What also needs to happen is for `dset' to get folded into sysinstall
so that the second kernel to come off the bindist can also be tweaked
to track whatever changes the user had to make in coming up off the
floppy.

						Jordan