From nobody Mon Aug 22 15:11:43 2022 X-Original-To: freebsd-current@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 4MBG5l5Xgdz4Zs4C for ; Mon, 22 Aug 2022 15:11:07 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4MBG5l56Jqz3Dnr; Mon, 22 Aug 2022 15:11:07 +0000 (UTC) (envelope-from kevans@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1661181067; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=X/WTkUZWX67xuoPtQJTdCun5P9dNXfgp25kOa/aa+M4=; b=kSOk9l5vfS6NSWEL1qZYJ4E3eoK8HkYPSS3Dbc8qsIasyZelxpwxvgLMnzDIgfnkayel3q tjYWZlxMwz+cM1gig0RfUN7YamGdAxbXGse7ay8vMZYNrGj5EgKO2QAdmAcWyMeck3VC6X NBuAkwZp3+X8IgBMWM0ICGfqPTkY4HyuaYX7e/6vAlrAMycBq6PXysV/MZdywQlxR+Vw6p ZPgA5+paTynhT86QxB71TQx2rFtjRR2bjUjJG9KaWgU3DGYMfx6E/DkEioUxRF+8H4U4P+ m4EBEt4nW7gY0fLh6FMAd1rQxfcDBrSWUv7j+9P6VDZGlbjdpdeYZnuaDBuSUw== Received: from mail-qt1-f178.google.com (mail-qt1-f178.google.com [209.85.160.178]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 4MBG5l3wPHz1SDG; Mon, 22 Aug 2022 15:11:07 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qt1-f178.google.com with SMTP id h21so8092014qta.3; Mon, 22 Aug 2022 08:11:07 -0700 (PDT) X-Gm-Message-State: ACgBeo1offAPyYvSXsbUx8LlvU5jD9u+1LJp+AuLGDAed3rknMMwDcaY Q3rPrWStZ0uKITAEBXaexgkEm5iX/EeT0ZPkclc= X-Google-Smtp-Source: AA6agR7SrptfLst14op+nKfdBdcrDRcNRJXdaCgv3h2GT8qJqv4NXaR8sFIRCmY3LR57zt6tu354NIlt8jB5CBVBv0Y= X-Received: by 2002:a05:622a:11d6:b0:343:5e19:7488 with SMTP id n22-20020a05622a11d600b003435e197488mr15829489qtk.476.1661181067128; Mon, 22 Aug 2022 08:11:07 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <01000182ac3b8593-fb381303-5719-4863-8fda-2530efcab31b-000000@email.amazonses.com> <2818f3da-3ae2-e6e3-9282-8b62263fb5f3@FreeBSD.org> <623263165.219.1661170200563@localhost> In-Reply-To: <623263165.219.1661170200563@localhost> From: Kyle Evans Date: Mon, 22 Aug 2022 08:11:43 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Beadm can't create snapshot To: Ronald Klop Cc: Peter Jeremy , freebsd-current@freebsd.org, Ryan Moeller , "Patrick M. Hausen" Content-Type: text/plain; charset="UTF-8" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1661181067; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=X/WTkUZWX67xuoPtQJTdCun5P9dNXfgp25kOa/aa+M4=; b=urjXj+DsyLWNPH828TNnFTc0mZpFolvsyvwbFYWkKEyKoqvB8yH2kN5QaWd6vvxwPp1+xn SJ7SPErO15Yzlq6RUPGRnGckoPcONAN4zMQtFyE0e9iW+NXf0gt2haHEJ+uK+NIFFGmr7B uW6YJ7CnDMDt71JBYGrq9UDGL2yNC1DcMa1U7vGs8KF8jpB1PnVRuZr3fOUWyQ3FzMUbE2 Cf77Ghnd8LZ048SwPVLt2uZEYJeSpazHeapblltgU4uUfJNZllQIgpJTtCisG5YBwXJ1hq Dp65LVQjDDgnPqTXXgCs4LCmm0zv1ZMJhdYusgPVAR3EAeK644M6aYP2hc9Ghw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1661181067; a=rsa-sha256; cv=none; b=C/eKt/M29a3NDcEK3XucP3qRjlnt36JmBZAGHhu3fQJhZK1rvCYBrSR2P62Iu6szSAeujM bnm3MCPGK5SjO30KpTCbRnYPjAujaLQNMsIPfzTt5m1U9mt9HCA9/Fn3dCkcK6K6LzFmFa lLn0NhOiBF738XXZg1YJuJgwuGji+u7YLuzbXaTpzRu0I2+AbUZSorR8+Ufp8U+dWV5WOk N0mecEhBdLTh0zt/aQzyW1MdvnSbqMyXLMt33TU/QBRNKq6kEATlpnkuKgF8BFpjSyOlU0 DFL1CmGOhZNwH9p+on9MbEmgZ553OZCpRtSS3nAgwSx/dNChilmFKMY/M5Hdcg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N On Mon, Aug 22, 2022 at 5:10 AM Ronald Klop wrote: > > > > Van: Peter Jeremy > Datum: maandag, 22 augustus 2022 10:45 > Aan: "Patrick M. Hausen" > CC: Ryan Moeller , freebsd-current@freebsd.org > Onderwerp: Re: Beadm can't create snapshot > > On 2022-Aug-17 18:07:20 +0200, "Patrick M. Hausen" wrote: > >Isn't beadm retired in favour of bectl? > > bectl still has a number of bugs: > 1) The output from "bectl list" is in filesystem/bename order rather > than creation date order. This is an issue if you use (eg) git > commit hashes as the name. > 2) "bectl activate" doesn't update /boot/loader.conf so the wrong > root filesystem is mounted. > > That said "bectl create" appears to be a workable replacement for > "beadm create" and avoids the current "'snapshots_changed' is > readonly" bugs. > > -- > Peter Jeremy > ________________________________ > > > > > Hi, > > From man bectl: > activate [-t | -T] beName > Activate the given beName as the default boot filesystem. If > the -t flag is given, this takes effect only for the next boot. > Flag -T removes temporary boot once configuration. Without > temporary configuration, the next boot will use zfs dataset > specified in boot pool bootfs property. > > So it uses the bootfs property instead of loader.conf. If beadm used a different mechaniscm it would by nice to mention that in the HISTORY section of the bectl man page. > I was not aware that beadm touches loader.conf, but I find that slightly horrifying. I won't personally make bectl do that, but I guess I could at least document that it doesn't...