Date: Mon, 12 Sep 2022 19:51:16 +0000 From: Thomas Laus <lausts@acm.org> To: freebsd-current@freebsd.org Subject: Re: Beadm can't create snapshot Message-ID: <0100018333418770-45f3584b-6271-4b63-9933-d548b812a4fb-000000@email.amazonses.com> In-Reply-To: <5cb26532-11d6-60cb-bbd8-4fa99db83a32@FreeBSD.org> References: <01000182ac3b8593-fb381303-5719-4863-8fda-2530efcab31b-000000@email.amazonses.com> <01000182e9f49b75-35f2fff9-c6f9-4b37-8e4c-263309620d31-000000@email.amazonses.com> <d8e176da-306d-7c99-2a94-10fb178a7b3b@FreeBSD.org> <5cb26532-11d6-60cb-bbd8-4fa99db83a32@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0100018333418770-45f3584b-6271-4b63-9933-d548b812a4fb-000000>