From owner-freebsd-current Sun Jan 21 23:47:16 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 401BE37B401; Sun, 21 Jan 2001 23:46:57 -0800 (PST) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.1/8.11.1) with ESMTP id f0M7ku906193; Mon, 22 Jan 2001 00:46:56 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101220746.f0M7ku906193@harmony.village.org> To: John Baldwin Subject: Re: lastest kernel from cvs ( sh exists with signal 8 ) Cc: "Donald J . Maddox" , Peter Wemm , The Hermit Hacker , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sun, 21 Jan 2001 23:35:49 PST." References: Date: Mon, 22 Jan 2001 00:46:56 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message John Baldwin writes: : 2) It hides the output from config(8). config(8) prints out all sorts of : useful warnings when options are deprecated, etc., but buildkernel hides these : from the user. The problem is that config(8) is by design an interactive tool, : which buildkernel fails to take into account. The hack now is to have : config(8) treat warnings as errors instead. :-/ config is not an interactive tool, any more than the compiler is an interactive tool. buildkernel hiding it from the user is a bug in buildkernel. It should be fixed. You shouldn't throw the baby out with the bath water. buildkernel is a much simplified way of telling people how to build kernels. As someone in the front lines of that game, I can tell you that the support load from that has dropped off quite a bit since we started telling people to use it. If you want to advocate all the steps that make it safe by hand, feel free, but the average user had no need to know them, nor do them by hand. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message