From owner-freebsd-questions@freebsd.org Wed Jun 20 18:47:50 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7B1B61003B26 for ; Wed, 20 Jun 2018 18:47:50 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [217.72.192.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BB4006CE77 for ; Wed, 20 Jun 2018 18:47:49 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([92.195.97.38]) by mrelayeu.kundenserver.de (mreue102 [212.227.15.183]) with ESMTPA (Nemesis) id 0LmcYl-1g4Uve1ryl-00aFU2; Wed, 20 Jun 2018 20:47:41 +0200 Date: Wed, 20 Jun 2018 20:47:40 +0200 From: Polytropon To: Mark Saad Cc: "Igor V. Ruzanov" , freebsd-questions@freebsd.org Subject: Re: Refresh my memory make release with a custom kernel Message-Id: <20180620204740.5de3d872.freebsd@edvax.de> In-Reply-To: References: <1DD85328-F718-4569-9BE8-811D34CBD779@longcount.org> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:nWbf/I88xrv9Bay9mapY/5Xm78DaWQxJYuWUMlNA+I2DngppWMo /D3VcAuRX3Ry7e3Fp3+PYkZXDRZD8B9se2NJPBssz34l/98GNcKqYBBysS3pcoTNRAl1OWB QjiDRCZTmnbrvxHRlD3KT8knwG+1H2s2Rys4W1pzNVspkpEUAPRdU7I46UUoUuydcn1NLmy nojLv9F6cp2ItlYc039XQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:GoIOvxAxRUE=:zdSwwtIRv9CKXal7+9CZvK MkcPqOSdOhkrxyLGdtVGSz3PQAfoJDfpatF7Icgya2ZaCVsuWVki29TmaRWKCCQZ5tn97CTe/ q+BVKxdTFG2/Z0Xwa9SijVT7/toqfL6N6rN059BCt0Wr3+KP42kjlP653rdjQW+JYG8Y9aCIM sdMAFm6yhiG7O0ttvRdj6U04U4vmYKhQOFd6gqu5CLua6WMxoyCtaCgXKHjCtnpxH73tkHlDt Ra0zENDQkHHjbZl7LPdgQY6wyEyAxKQUq+TwE5gNxFY8XnIHzxh3xN2aWY+PPe5xiYuuOMsTu R4xA506Ip/OIr2l2Ywpa0jQfa6FnhTNi3GPxqi4bFwRcXVznPcXbd3rJVlhn94XzZDfb0JtOr xBopt/uH2MG0UhsnhV0pyS+pF9kI6dABPZQ5Num7bNoO9jyfRYVwhVkGR13BVuKprFR3Kb655 X1tsOnmU9A0Zbph00Ph3DLkES3ShnmgqVN//n580y7Lz+XmZA3yGUmSJ9utbGodHctg1Q4LJ+ C/YiiuD9h6QB1swAj9y+lX9BGBc2C/fERqjsgWGJDcr8t36a4aRaw2/3+nq8jBEISfleM/gUd z82EWOcRqKUNi97Qva5zhKBqllFD1vgjsVenguBpBrejsTa5+eEHEbyt4myvLWD0z/XgdIcP/ H2IC5fnOfuKuUfOYtGXdXXN3sRC9Uvi/F7wpVhSlGFqDYun2sZOggB76XGjqHS1SKTX8tiFEn 1+78ba2T0q5EWwsR X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jun 2018 18:47:50 -0000 On Wed, 20 Jun 2018 13:26:34 -0400, Mark Saad wrote: > Igor > That did not work, the resulting kernel was still a GENERIC . For a > work around > I am just going to tar up /boot/kernel into my own kernel.txz. This is > on 11.2-SATBLE/PRERELEASE >From what I understood from the Makefiles, "make release" will always build with the GENERIC kernel configuration. There are basically two possibilities: a) overwrite GENERIC with your own configuration, or b) previously run "make buildkernel KERNCONF=", tar the result from /usr/obj, then build the release, and finally replace its GENERIC objects with your own ones. See "man 7 release" for details. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...