Date: Wed, 24 May 2023 19:46:13 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> To: Vitaliy Gusev <gusev.vitaliy@gmail.com> Cc: virtualization@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: BHYVE SNAPSHOT image format proposal Message-ID: <fbc49e54-181c-f57f-c1eb-431c32f1da20@quip.cz> In-Reply-To: <AF34E648-2D8A-46C7-82A5-B88006BBB8F6@gmail.com> References: <67FDC8A8-86A6-4AE4-85F0-FF7BEF9F2F06@gmail.com> <CAFYkXjng1LWy5wVyTnSo0xrEWOy%2BOx9ZjLcmFqQs5EVpT8J_uA@mail.gmail.com> <AF34E648-2D8A-46C7-82A5-B88006BBB8F6@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 24/05/2023 17:10, Vitaliy Gusev wrote: >>> Current snapshot implementation has disadvantages: >>> 3 files per snapshot: .meta, .kern, vram >> >> No problem, unless new single file will be protected against >> corruption (filesystem, transfer, application crash) and possible to >> be easily and cheaply modified in place? > > Current snapshot implementation doesn’t have it. I would say more, current > pkg implementation doesn’t track/notify if some of files are changed. > Binary files on a > system can be changed, for example ELF files, without any notification. pkg stores checksums for installed files. You can check them with pkg check -s -a or pkg check --checksums -a. Changes are reported by daily periodic script. Kind regards Miroslav Lachman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fbc49e54-181c-f57f-c1eb-431c32f1da20>