From owner-freebsd-current  Fri Jan 30 05:35:21 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id FAA00104
          for current-outgoing; Fri, 30 Jan 1998 05:35:21 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA29994
          for <freebsd-current@FreeBSD.ORG>; Fri, 30 Jan 1998 05:35:13 -0800 (PST)
          (envelope-from jkh@time.cdrom.com)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id FAA20164; Fri, 30 Jan 1998 05:34:05 -0800 (PST)
To: Mike Smith <mike@smith.net.au>
cc: Charlie ROOT <root@korin.warman.org.pl>, freebsd-current@FreeBSD.ORG
Subject: Re: /kernel.config takes over boot: -c :-(( 
In-reply-to: Your message of "Fri, 30 Jan 1998 23:11:02 +1030."
             <199801301241.XAA04329@word.smith.net.au> 
Date: Fri, 30 Jan 1998 05:34:04 -0800
Message-ID: <20160.886167244@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current"

> I would be inclined to say that the "expected" behaviour would be to 
> have userconfig *not* exit after reading the kernel.config data *if* -c 
> was supplied. 

Fine, if you want to add the ability to tell the difference between
being invoked with -c or compiled with USERCONFIG_BOOT, go for it! :-)

					Jordan