From owner-freebsd-questions@freebsd.org Wed Nov 7 09:29:48 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 92D3411217CE for ; Wed, 7 Nov 2018 09:29:48 +0000 (UTC) (envelope-from 4250.10.freebsd-questions=freebsd.org@email-od.com) Received: from s1-b0c6.socketlabs.email-od.com (s1-b0c6.socketlabs.email-od.com [142.0.176.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7D07189BEC for ; Wed, 7 Nov 2018 09:29:47 +0000 (UTC) (envelope-from 4250.10.freebsd-questions=freebsd.org@email-od.com) DKIM-Signature: v=1; a=rsa-sha256; d=email-od.com;i=@email-od.com;s=dkim; c=relaxed/relaxed; q=dns/txt; t=1541582987; x=1544174987; h=content-transfer-encoding:content-type:mime-version:references:in-reply-to:message-id:subject:cc:to:from:date:x-thread-info; bh=S4Q2N3hVys/Zjwqu/7IlLZMhmDAZYxlrUbGPv/ImUbc=; b=Uk6PdF15UccPERdfp47gKHonquBRZrcGrXTmTWtdWdCoWbpCJaDlTRvIPv/SqIiVky75WlPyOTcQ3my0TJGKkTJTWGWwQz/I3ymdrcrxMV/9xqQQninDqzHB6M9qOwJEuvJ4ID1aNHl4JWF4C5rPIctXd3ZXqeDqCNCxEK35gmU= X-Thread-Info: NDI1MC4xMi4xOWYwMDAwMDFiNWNhNDIuZnJlZWJzZC1xdWVzdGlvbnM9ZnJlZWJzZC5vcmc= Received: from r1.us-east.aws.in.socketlabs.com (r1.us-east.aws.in.socketlabs.com [54.86.145.87]) by mxsg2.email-od.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Wed, 7 Nov 2018 04:29:41 -0500 Received: from smtp.lan.sohara.org (EMTPY [89.127.62.20]) by r1.us-east.aws.in.socketlabs.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Wed, 7 Nov 2018 04:29:32 -0500 Received: from [192.168.63.1] (helo=steve.lan.sohara.org) by smtp.lan.sohara.org with smtp (Exim 4.91 (FreeBSD)) (envelope-from ) id 1gKK9T-000JPF-0p; Wed, 07 Nov 2018 09:29:31 +0000 Date: Wed, 7 Nov 2018 09:29:30 +0000 From: Steve O'Hara-Smith To: Aram =?UTF-8?B?SMSDdsSDcm5lYW51?= Cc: freebsd-questions@freebsd.org Subject: Re: freebsd-update(8) and custom kernels Message-Id: <20181107092930.3f48e1cee7caeb670fe38a58@sohara.org> In-Reply-To: References: <20181106170818.GD88460@mordor.lan> <20181106174215.43746c0a0f28d86dd4ef0e14@sohara.org> <20181106223828.4e65f87c884b43c40f0231e3@sohara.org> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 7D07189BEC X-Spamd-Result: default: False [-2.77 / 200.00]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:142.0.176.0/20]; MV_CASE(0.50)[]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[email-od.com:+]; MX_GOOD(-0.01)[cached: mxbh.socketlabs.com]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.84)[-0.845,0]; FORGED_SENDER(0.00)[steve@sohara.org,4250.10.freebsd-questions=freebsd.org@email-od.com]; RCVD_TLS_LAST(0.00)[]; IP_SCORE(-0.02)[country: US(-0.09)]; ASN(0.00)[asn:7381, ipnet:142.0.176.0/22, country:US]; FROM_NEQ_ENVFROM(0.00)[steve@sohara.org,4250.10.freebsd-questions=freebsd.org@email-od.com]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.95)[-0.951,0]; R_DKIM_ALLOW(-0.20)[email-od.com]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-0.95)[-0.947,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[sohara.org]; FORGED_SENDER_VERP_SRS(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[198.176.0.142.list.dnswl.org : 127.0.15.0]; ENVFROM_VERP(0.00)[] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Nov 2018 09:29:48 -0000 On Wed, 7 Nov 2018 00:12:29 +0100 Aram Hăvărneanu wrote: > > Building the kernel doesn't need the new binaries, otherwise a > > source upgrade would be impossible. > > I was under the impression that building across releases was not > recommended and/or fragile. From /usr/src/UPDATING: Only across some boundaries. > This is how Julian said it works for him with the custom kernel, > except I replaced fetch with upgrade: This is now almost exactly what I do for upgrades on the box with a custom kernel (the only difference is that I have the KERNCONF enshrined in make.conf and so don't specify it). > 1) freebsd-update -r XX.Y-RELEASE upgrade > 2) freebsd-update install > 3) make kernel KERNCONF=MYKERNEL > 4) reboot > 5) freebsd-update install > > In my understanding in step #3 you don't have the new sources yet, > so how do you compile the new kernel? Or do you have them? I never checked, I can only assume that they must be there. I'll try and remember to look next time I do one. It does make sense to defer as little as possible to the post-reboot install if only for this reason. -- Steve O'Hara-Smith | Directable Mirror Arrays C:\>WIN | A better way to focus the sun The computer obeys and wins. | licences available see You lose and Bill collects. | http://www.sohara.org/