From owner-freebsd-current Sun Jan 21 23:13:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from moby.geekhouse.net (moby.geekhouse.net [64.81.6.36]) by hub.freebsd.org (Postfix) with ESMTP id C454C37B401 for ; Sun, 21 Jan 2001 23:12:53 -0800 (PST) Received: from laptop.baldwin.cx (john@dhcp150.geekhouse.net [192.168.1.150]) by moby.geekhouse.net (8.11.0/8.9.3) with ESMTP id f0M7HGs79420; Sun, 21 Jan 2001 23:17:16 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010122015502.A18847@cae88-102-101.sc.rr.com> Date: Sun, 21 Jan 2001 23:12:44 -0800 (PST) From: John Baldwin To: "Donald J . Maddox" Subject: Re: lastest kernel from cvs ( sh exists with signal 8 ) Cc: freebsd-current@FreeBSD.org, The Hermit Hacker , Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Jan-01 Donald J . Maddox wrote: > On Sun, Jan 21, 2001 at 10:49:30PM -0800, Peter Wemm wrote: >> >> Argh! I wish people would stop using buildkernel! :-( It calls config(8) >> in such a way that buries the warning messages where people dont see. >> config(8) is meant to be used interactively :-( > > Is there another target that will get a kernel built with new tools > in /usr/obj rather than old, previously installed binaries? Rarely if ever do you need the new tools. The only cases are for a binutils upgrade that is not backwards compatible (such as the 2.9 -> 2.10 upgrade), or if you need a newer version of config, which can be handled by installing config and then building your kernel. The config(8) changes won't happen in stable, and I don't foresee anymore drastic buildkernel changes in the future. FWIW, I _never_ use buildkernel to update my kernels on any of my boxes. I just do it the old fashioned way, and with the exception of the 2.9 -> 2.10 binutils upgrade, it always works. buildkernel overloads the KERNEL variable and thus violates POLA, so it needs fixing regardless, but I don't see a reason to encourage its use unless it is actually needed. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message