From owner-freebsd-stable Mon Jul 10 0:35:26 2000 Delivered-To: freebsd-stable@freebsd.org Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131]) by hub.freebsd.org (Postfix) with ESMTP id 959FF37B7A7; Mon, 10 Jul 2000 00:35:21 -0700 (PDT) (envelope-from ust@cert.siemens.de) X-Envelope-Sender-Is: ust@cert.siemens.de (at relayer goliath.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by goliath.siemens.de (8.10.1/8.10.1) with ESMTP id e6A7ZKB22566; Mon, 10 Jul 2000 09:35:20 +0200 (MET DST) Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17]) by mail1.siemens.de (8.10.1/8.10.1) with ESMTP id e6A7ZJh22175; Mon, 10 Jul 2000 09:35:19 +0200 (MET DST) Received: from alaska.cert.siemens.de (reims.mchp.siemens.de [139.23.202.134]) by mars.cert.siemens.de (8.10.2/8.10.2/Siemens CERT [ $Revision: 1.8 ]) with ESMTP id e6A7ZJX53579; Mon, 10 Jul 2000 09:35:19 +0200 (CEST) Received: (from ust@localhost) by alaska.cert.siemens.de (8.10.2/8.10.2/alaska [ $Revision: 1.4 ]) id e6A7ZJv52969; Mon, 10 Jul 2000 07:35:19 GMT Date: Mon, 10 Jul 2000 09:35:19 +0200 From: Udo Schweigert To: Kris Kennaway Cc: stable@FreeBSD.ORG Subject: Re: HEADS UP! Always use the 'make buildkernel' target to make yer kernels Message-ID: <20000710093519.A52878@alaska.cert.siemens.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from kris@FreeBSD.ORG on Sun, Jul 09, 2000 at 08:49:50PM -0700 X-Operating-System: FreeBSD 4.0-STABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 09, 2000 at 20:49:50 -0700, Kris Kennaway wrote: > Subject basically says it all. "make buildkernel KERNEL=" and > "make installkernel KERNEL=" (or set KERNEL in /etc/make.conf or > the environment, where KERNEL is the name of the kernel to build (GENERIC, > etc)) are what you should always be using to build your kernels, unless > you know what you're doing. > I found it was a good idea (by experience), to always have an up to date version of the GENERIC-kernel available in /. Since it is possible to build two kernel by saying # make buildkernel KERNEL="mykernel GENERIC" it would also be nice to have the possibility to install both new kernels to / (instead of only installing the first) by saying # make installkernel KERNEL="mykernel GENERIC" Attached you find a patch to do this. Best regards. -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 ZT IK 3, Siemens CERT | Fax : +49 89 636 41166 D-81730 Muenchen / Germany | email : ust@cert.siemens.de PGP-2/5 fingerprint | D8 A5 DF 34 EC 87 E8 C6 E2 26 C4 D0 EE 80 36 B2 --- Makefile.inc1.orig Sun Jul 2 13:00:19 2000 +++ Makefile.inc1 Mon Jul 10 09:25:36 2000 @@ -356,13 +356,11 @@ .endif BUILDKERNELS= -INSTALLKERNEL= +INSTALLKERNELS= .for _kernel in ${KERNEL} .if exists(${KRNLCONFDIR}/${_kernel}) BUILDKERNELS+= ${_kernel} -.if empty(INSTALLKERNEL) -INSTALLKERNEL= ${_kernel} -.endif +INSTALLKERNELS+= ${_kernel} .endif .endfor @@ -393,12 +391,14 @@ # # installkernel # -# Install the kernel defined by INSTALLKERNEL +# Install the kernels defined by INSTALLKERNELS # installkernel: - cd ${KRNLOBJDIR}/${INSTALLKERNEL}; \ - ${IMAKEENV} MACHINE=${MACHINE} KERNEL=${INSTALLKERNEL} \ +.for _kernel in ${INSTALLKERNELS} + cd ${KRNLOBJDIR}/${_kernel}; \ + ${IMAKEENV} MACHINE=${MACHINE} KERNEL=${_kernel} \ ${MAKE} install +.endfor # # update To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message