From owner-freebsd-questions@freebsd.org Tue Nov 6 16:02:17 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 0CE211128597 for ; Tue, 6 Nov 2018 16:02:17 +0000 (UTC) (envelope-from aram.h@mgk.ro) Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1857E7D8B5 for ; Tue, 6 Nov 2018 16:02:15 +0000 (UTC) (envelope-from aram.h@mgk.ro) Received: by mail-qt1-x829.google.com with SMTP id r14so3157105qtp.1 for ; Tue, 06 Nov 2018 08:02:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mgk-ro.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=heTLuZowG3FaC5ZcX1o0UHN0Ezd1wS6la3CCG9ShGaw=; b=Yy5bH2JmneFXVZbwR9zzUNhYVK6+r1Ksd7t8xl9Zfu0+nDztQX95y9qhpYbobu3mF8 3ihPrXUDA38aCL8bpWDZhrAOkNcj3YsLsWCeQkuFM8+HzRwk0Us1l3M4lUfa3suM6pXR nY6eS9zj0FmBngdBQsA7NfwTP/NRMlFNyQFL55AUDVTQs6vyZUyBTMDYAK/bTfs7LQN7 fRSvyrn2QGanP1/pGg7SPAXbEIetMMKdXDB76IizGCXj6byOCS4sCZwcxNv/GCOAE9Sv wUjARWpfua9gAOfxKqFO4oMVLAgRym8hBqHxxcuyVGAVWW0Ut1YZl3adtTEnaxbSnExs 8eFw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=heTLuZowG3FaC5ZcX1o0UHN0Ezd1wS6la3CCG9ShGaw=; b=Iy3hN1wAM/fKYkcz1HZA1C8o05UkwGc0dh4ahILRarPGQ7S+789YvSIrs/YB0d7EhH z7X/hdqqYr6ZMb8T9kVq/64FRS7YDSoUj5zTpqDEnpF/xMVHYbr2G58oDfGyistMjnlW ZXg6oJpXWrmzdN82HfMoe4HI4mKau5aDxdipWWgZIGudaOUJoOapZ8ixChz2yIFrS9LT 0R8VzFUE2u1HedSB3lORcotbvmO1F2jGq+YJYaWgwUWOmc3kM1wwCjPQfnsTJgbiVu8w I1dQu9p1uYjjQBt6QNZiFlRYIyt+Uge+5vOofle3JKh91su3OE8BMPJWJ9osgAFFm19M hgbw== X-Gm-Message-State: AGRZ1gLx75el8mwS9QArUkVbbg2Y8+KYtLJ2D7nP2SdUx9IadCBNs2ci ukKlaZGbJrLE9IXBwhZCdpQLr6LRppoRWt+51daVmiFAHbA= X-Google-Smtp-Source: AJdET5cgfkbhtEjGpdg/eeL+NFDIuUxhHtjiTMSxArntjiOL9cyuyuWo/THfQfoc5r9ULHZf0jdfRrfX3zDxMCsDuDc= X-Received: by 2002:a0c:ec50:: with SMTP id n16mr27027945qvq.105.1541520134487; Tue, 06 Nov 2018 08:02:14 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a0c:9dd2:0:0:0:0:0 with HTTP; Tue, 6 Nov 2018 08:01:54 -0800 (PST) From: =?UTF-8?B?QXJhbSBIxIN2xINybmVhbnU=?= Date: Tue, 6 Nov 2018 17:01:54 +0100 Message-ID: Subject: freebsd-update(8) and custom kernels To: freebsd-questions@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 1857E7D8B5 X-Spamd-Result: default: False [-2.98 / 200.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.85)[-0.850,0]; R_DKIM_ALLOW(-0.20)[mgk-ro.20150623.gappssmtp.com]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.82)[-0.822,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[3]; DMARC_NA(0.00)[mgk.ro]; DKIM_TRACE(0.00)[mgk-ro.20150623.gappssmtp.com:+]; MX_GOOD(-0.01)[alt1.aspmx.l.google.com,aspmx.l.google.com,alt2.aspmx.l.google.com]; RCVD_IN_DNSWL_NONE(0.00)[9.2.8.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.48)[-0.477,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; IP_SCORE(-0.53)[ipnet: 2607:f8b0::/32(-1.18), asn: 15169(-1.37), country: US(-0.08)]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] 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: Tue, 06 Nov 2018 16:02:17 -0000 Hello, The FreeBSD handbook claims that freebsd-update(8) will leave custom kernels alone, and that if using a custom kernel it will update /boot/GENERIC to the release kernel if it exists. It also hints that it uses this /boot/GENERIC for upgrades between releases, allowing you to install your custom kernel post-upgrade after you will have rebuilt it. This is not what's happening at all, instead freebsd-update(8) is trashing custom kernels without warning. There have been several threads about this on the mailing list. The only conclusion I have been able to draw from them is that the handbook is out of date. Apparently the current, undocumented behavior dates back at least six years. So, is it possible to track -RELEASE using freebsd-update(8) and still use custom kernels? Of course I can remove "kernel" from "Components" in freebsd-update.conf and then freebsd-update(8) won't overwrite my kernel, but I would imagine I won't be able to upgrade between releases that way, since freebsd-update(8) will not provide an intermediary newer n+1 GENERIC kernel to boot the new n+1 release. What's the solution here? Is there one? Thanks, --=20 Aram H=C4=83v=C4=83rneanu