From nobody Mon Sep 12 19:51:16 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 4MRHKK6S08z4c8N2 for ; Mon, 12 Sep 2022 19:51:17 +0000 (UTC) (envelope-from 0100018333418770-45f3584b-6271-4b63-9933-d548b812a4fb-000000@amazonses.com) Received: from a48-89.smtp-out.amazonses.com (a48-89.smtp-out.amazonses.com [54.240.48.89]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4MRHKK0QhBz3bGC for ; Mon, 12 Sep 2022 19:51:17 +0000 (UTC) (envelope-from 0100018333418770-45f3584b-6271-4b63-9933-d548b812a4fb-000000@amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1663012276; h=Message-ID:Date:MIME-Version:Subject:To:References:From:In-Reply-To:Content-Type:Content-Transfer-Encoding:Feedback-ID; bh=J5mwZo6sPDZ4e2nndIfLimFFyomfcTGyQyMxJeqpNco=; b=DKsSAHvFwu7YYjd607cLd4vyYd0uX7q1Skbh3PFbLcV8et9SKoOVr6VOidm28Vpl MTzGeTHAH+DHaIpHP5j9uB/5npi7FjQxHKtjlROJYrAljVTXppzV2NsUpPa/4obUlfC yXkwJubFLTd1WHOxDeFOlhvQlIl2SyPecHD8ts/0= Message-ID: <0100018333418770-45f3584b-6271-4b63-9933-d548b812a4fb-000000@email.amazonses.com> Date: Mon, 12 Sep 2022 19:51:16 +0000 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 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:91.0) Gecko/20100101 Thunderbird/91.13.0 Subject: Re: Beadm can't create snapshot Content-Language: en-US To: freebsd-current@freebsd.org References: <01000182ac3b8593-fb381303-5719-4863-8fda-2530efcab31b-000000@email.amazonses.com> <01000182e9f49b75-35f2fff9-c6f9-4b37-8e4c-263309620d31-000000@email.amazonses.com> <5cb26532-11d6-60cb-bbd8-4fa99db83a32@FreeBSD.org> From: Thomas Laus In-Reply-To: <5cb26532-11d6-60cb-bbd8-4fa99db83a32@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Feedback-ID: 1.us-east-1.9pbSdi8VQuDGy3n7CRAr3/hYnLCug78GrsPo0xSgBOs=:AmazonSES X-SES-Outgoing: 2022.09.12-54.240.48.89 X-Rspamd-Queue-Id: 4MRHKK0QhBz3bGC X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=amazonses.com header.s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw header.b=DKsSAHvF; dmarc=fail reason="SPF not aligned (relaxed), DKIM not aligned (relaxed)" header.from=acm.org (policy=none); spf=pass (mx1.freebsd.org: domain of 0100018333418770-45f3584b-6271-4b63-9933-d548b812a4fb-000000@amazonses.com designates 54.240.48.89 as permitted sender) smtp.mailfrom=0100018333418770-45f3584b-6271-4b63-9933-d548b812a4fb-000000@amazonses.com X-Spamd-Result: default: False [0.52 / 15.00]; FORGED_MUA_THUNDERBIRD_MSGID_UNKNOWN(2.50)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.75)[-0.749]; FORGED_SENDER(0.30)[lausts@acm.org,0100018333418770-45f3584b-6271-4b63-9933-d548b812a4fb-000000@amazonses.com]; R_SPF_ALLOW(-0.20)[+ip4:54.240.0.0/18]; R_DKIM_ALLOW(-0.20)[amazonses.com:s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw]; NEURAL_HAM_LONG(-0.13)[-0.133]; DMARC_POLICY_SOFTFAIL(0.10)[acm.org : SPF not aligned (relaxed), DKIM not aligned (relaxed),none]; MIME_GOOD(-0.10)[text/plain]; RCVD_COUNT_ZERO(0.00)[0]; ARC_NA(0.00)[]; ASN(0.00)[asn:14618, ipnet:54.240.48.0/23, country:US]; MIME_TRACE(0.00)[0:+]; FROM_NEQ_ENVFROM(0.00)[lausts@acm.org,0100018333418770-45f3584b-6271-4b63-9933-d548b812a4fb-000000@amazonses.com]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; DKIM_TRACE(0.00)[amazonses.com:+]; FROM_HAS_DN(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[54.240.48.89:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; DWL_DNSWL_NONE(0.00)[amazonses.com:dkim] X-ThisMailContainsUnwantedMimeParts: N On 9/12/22 05:29, Ryan Moeller wrote: > > Here's the patch for the kernel and brief instructions: > > https://reviews.freebsd.org/P547 > That worked. I was not familiar with patching a file using git. My experience has always used the 'patch' utility and a unified diff. I just made a backup of the file, copied and pasted the change to the original file and compiled a new kernel. After rebooting, I was able to use 'beadm' to create a new snapshot. I revisited the file and removed the changes and recompiled the kernel. All is good Thanks Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF