From nobody Tue May 26 08:46:07 2026 X-Original-To: freebsd-stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4gPmYx2MZYz6fccG for ; Tue, 26 May 2026 08:46:13 +0000 (UTC) (envelope-from qqyr7xx9k@shirt.ocn.ne.jp) Received: from ocn-ckd-mts-208c37.ocn.ad.jp (ocn-ckd-mts-208c37.ocn.ad.jp [125.170.88.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4gPmYw5NS5z49Sf for ; Tue, 26 May 2026 08:46:12 +0000 (UTC) (envelope-from qqyr7xx9k@shirt.ocn.ne.jp) Authentication-Results: mx1.freebsd.org; none Received: from ocn-spm-mts-202c1.ocn.ad.jp (ocn-spm-mts-202c1.ocn.ad.jp [210.145.246.201]) by ocn-ckd-mts-208c37.ocn.ad.jp (Postfix) with ESMTP id E6F2C40005EC; Tue, 26 May 2026 17:46:07 +0900 (JST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=shirt.ocn.ne.jp; s=20240118; t=1779785167; bh=2L2LlBqw7uagaEKXvFoz8sdIORgpZASROwFL/klzC6k=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=e2pVttz8UPGNi65cgkwm/RZuGupOh+/LjhtmE+2MkD0xrY/2we7D8vRpVOzOlRb40 xFkCu4f3mAQl/5YZJCe3G0UhzKiMmOJ+LFRyaBGzhVib0kCwnwfXtpv0EyAF+zrHE/ Ldep6tRhIkucXaTucuS0AXKDxSbVn5B5A2kg1gFo+3abQHLrql3jNFDV7FoAD8gHRz iLhfge0UjcGfvLWSv7WS7ZfKtzptPuf23RUpIgJkQdaNmIsvCWW5AWk0PzNOR0oxPq NXqq+YjF2RVxCFd4F5udRslJ7YthZKEvn/o/xEA3ipUicQAKnMLVD6mdsTz2RVDdw1 EPpKUAdqzZihw== Received: from ocn-vc-mts-208c1.ocn.ad.jp ([210.145.250.202]) by ocn-spm-mts-202c1 with ngmta id 488691d0-18b3112e353be782; Tue, 26 May 2026 17:46:07 +0900 Received: from ocn-sdpx-mts-207c1.ocn.ad.jp ([210.145.249.150]) by ocn-vc-mts-208c1 with ngmta id c65b9b3e-18b3112e2fcad8d6; Tue, 26 May 2026 17:46:07 +0900 Received: from [192.168.1.11] (p1634144-ipxg05401yosida.nagano.ocn.ne.jp [153.185.242.144]) by ocn-sdpx-mts-207c1.ocn.ad.jp (Postfix) with ESMTPA; Tue, 26 May 2026 17:46:07 +0900 (JST) Content-Type: multipart/alternative; boundary="------------Ubq0BmD8hG1zip0nNyuqfrZF" Message-ID: <62e4616f-e616-4339-9870-ba6f269ecfa9@shirt.ocn.ne.jp> Date: Tue, 26 May 2026 17:46:07 +0900 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Proposal: Improve BE naming convention in freebsd-update install To: Ronald Klop Cc: freebsd-stable@freebsd.org References: <70da0c5b-c865-44e9-8c19-abb1cd779efe@shirt.ocn.ne.jp> <1676824497.1245.1779783892574@localhost> Content-Language: en-US From: Takashi Shimizu In-Reply-To: <1676824497.1245.1779783892574@localhost> X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:4713, ipnet:125.170.0.0/16, country:JP] X-Rspamd-Queue-Id: 4gPmYw5NS5z49Sf X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated This is a multi-part message in MIME format. --------------Ubq0BmD8hG1zip0nNyuqfrZF Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 5/26/26 17:24, Ronald Klop wrote: > > *Van:* Takashi Shimizu > *Datum:* zondag, 24 mei 2026 13:53 > *Aan:* freebsd-stable@freebsd.org > *Onderwerp:* Proposal: Improve BE naming convention in freebsd-update > install > > > Hi, > > I've read the rest of the thread also but reply on this one as it > keeps the context of your question. > Bectl does not tell the user how to name the "active" BE. You can see > which is active by the |NR| parameters. > > You probably activated |15.0-RELEASE-p8_2026-05-21_183216| yourself in > the past and then it sticks with that name. Because that is the BE you > choose. > If you want it to have another name, you can easily rename it yourself > on your system. > > |bectl rename 15.0-RELEASE-p8_2026-05-21_183216 HEAD| > > After the next run of freebsd-update you will have a new timestamped > BE, but the active and updated one will still be named HEAD. 🥳 > > NB: Renaming a BE can give issues when using zfs send | zfs receive to > a backup system. As the names on the backup didn't change, the ZFS > filesystems+snapshots on the backup are out of sync now. > > Regards, > Ronald. Thank you for the suggestion. However, my proposal is not about how users name their BEs manually. It is specifically about the names that freebsd-update generates automatically. The target audience is users who do not actively manage their BEs and are not familiar with bectl. When something goes wrong after a freebsd-update run and they need to roll back urgently, they look at bectl list and have to figure out which BE to activate. At that moment, the automatically generated names are misleading and cost them valuable time. Users who carefully manage their own BEs, as you describe, are already handling this well and are not affected by this proposal. Takashi --------------Ubq0BmD8hG1zip0nNyuqfrZF Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit


On 5/26/26 17:24, Ronald Klop wrote:
 

Van: Takashi Shimizu <qqyr7xx9k@shirt.ocn.ne.jp>
Datum: zondag, 24 mei 2026 13:53
Aan: freebsd-stable@freebsd.org
Onderwerp: Proposal: Improve BE naming convention in freebsd-update install


Hi,

I've read the rest of the thread also but reply on this one as it keeps the context of your question.
Bectl does not tell the user how to name the "active" BE. You can see which is active by the NR parameters.

You probably activated 15.0-RELEASE-p8_2026-05-21_183216 yourself in the past and then it sticks with that name. Because that is the BE you choose.
If you want it to have another name, you can easily rename it yourself on your system.

bectl rename 15.0-RELEASE-p8_2026-05-21_183216 HEAD

After the next run of freebsd-update you will have a new timestamped BE, but the active and updated one will still be named HEAD. 🥳

NB: Renaming a BE can give issues when using zfs send | zfs receive to a backup system. As the names on the backup didn't change, the ZFS filesystems+snapshots on the backup are out of sync now.

Regards,
Ronald.
 

Thank you for the suggestion.

However, my proposal is not about how users name their BEs manually. It is specifically about the names that freebsd-update generates automatically.

The target audience is users who do not actively manage their BEs and are not familiar with bectl. When something goes wrong after a freebsd-update run and they need to roll back urgently, they look at bectl list and have to figure out which BE to activate. At that moment, the automatically generated names are misleading and cost them valuable time.

Users who carefully manage their own BEs, as you describe, are already handling this well and are not affected by this proposal.

Takashi

--------------Ubq0BmD8hG1zip0nNyuqfrZF--