From owner-freebsd-current Fri Jan 30 04:49:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA23545 for current-outgoing; Fri, 30 Jan 1998 04:49:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA23540 for ; Fri, 30 Jan 1998 04:49:23 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id XAA04329; Fri, 30 Jan 1998 23:11:02 +1030 (CST) Message-Id: <199801301241.XAA04329@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Jordan K. Hubbard" cc: Charlie ROOT , freebsd-current@FreeBSD.ORG Subject: Re: /kernel.config takes over boot: -c :-(( In-reply-to: Your message of "Fri, 30 Jan 1998 04:17:57 -0800." <19849.886162677@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Jan 1998 23:11:02 +1030 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > Like I said, I do understand what you essentially want, however, and > what that is is *another* flag (-C?) which tells UserConfig *not* to > pay attention to any provided parameters. :-) 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. Yes, I'll put a diff where my mouth is if that's what it takes. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\