From owner-freebsd-current Sun Jan 21 23:27:17 2001 Delivered-To: freebsd-current@freebsd.org Received: from Mail6.sc.rr.com (fe6.southeast.rr.com [24.93.67.53]) by hub.freebsd.org (Postfix) with ESMTP id 1948F37B402; Sun, 21 Jan 2001 23:26:59 -0800 (PST) Received: from sc.rr.com ([24.88.102.101]) by Mail6.sc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Mon, 22 Jan 2001 02:26:57 -0500 Received: (from dmaddox@localhost) by sc.rr.com (8.11.1/8.11.1) id f0M7Rv119148; Mon, 22 Jan 2001 02:27:57 -0500 (EST) (envelope-from dmaddox) Date: Mon, 22 Jan 2001 02:27:57 -0500 From: "Donald J . Maddox" To: John Baldwin Cc: "Donald J . Maddox" , freebsd-current@FreeBSD.org, The Hermit Hacker , Peter Wemm Subject: Re: lastest kernel from cvs ( sh exists with signal 8 ) Message-ID: <20010122022757.B18935@cae88-102-101.sc.rr.com> Reply-To: dmaddox@sc.rr.com Mail-Followup-To: John Baldwin , "Donald J . Maddox" , freebsd-current@FreeBSD.org, The Hermit Hacker , Peter Wemm References: <20010122015502.A18847@cae88-102-101.sc.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Sun, Jan 21, 2001 at 11:12:44PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, fair enough. I have to confess that my usual procedure remains, as it has been for a long time, like this: 1) rm -r /usr/include; cd /usr/src; make includes This may be controversial, but it has always worked for me, and although it's not supposed to (in my understanding), the build (I think both world and kernel) does use installed headers. If you don't think so, mv /usr/include and then try to build either. 2) cd usr.sbin/config; make obj && make depend && make && make install 3) config and build kernel 4) make buildworld 5) install kernel 6) make installworld 7) update /etc if necessary 8) reboot Here lately, I have been trying to break this cycle and use the 1) make buildworld 2) make buildkernel 3) make installkernel 4) make installworld 5) reboot cycle instead, since I have been assured that this is the canonical way of doing things now. It appears that these pronouncements were premature at best. On Sun, Jan 21, 2001 at 11:12:44PM -0800, John Baldwin wrote: > > 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