On Tue, Apr 11, 2023 at 07:33:19PM -0700, Eric Biggers wrote:
> On Mon, Apr 10, 2023 at 10:19:46PM -0700, Christoph Hellwig wrote:
> > Dave is going to hate me for this, but..
> >
> > I've been looking over some of the interfaces here, and I'm starting
> > to very seriously questioning the design
On Mon, Apr 10, 2023 at 10:19:46PM -0700, Christoph Hellwig wrote:
> Dave is going to hate me for this, but..
>
> I've been looking over some of the interfaces here, and I'm starting
> to very seriously questioning the design decisions of storing the
> fsverity hashes in xattrs.
>
> Yes, storing
gfs2-utils contains the tools needed to create, check, modify and
inspect gfs2 filesystems along with support scripts needed on every gfs2
cluster node.
This minor release includes fixes for a small number of issues
discovered in 3.5.0, including test failures that occur on 32-bit
This patch defines PKG_CONFIG make var which could be overwrite by the
user like it's the case for dlm_controld Makefile.
---
fence/Makefile | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/fence/Makefile b/fence/Makefile
index ee4dfb88..894f6396 100644
--- a/fence/Makefile
Currently make (GNU Make 4.2.1) will fail if pkg-config fails even if
it's not necessary, e.g. make clean target. We move the make bailout if
pkg-config failed to the binary target when pkg-config result is
necessary.
Note: this is using $(.SHELLSTATUS) which is only available on GNU Make
version
Currently make (GNU Make 4.2.1) will fail if pkg-config fails even if
it's not necessary, e.g. make clean target. We move the make bailout if
pkg-config failed to the binary target when pkg-config result is
necessary.
Note: this is using $(.SHELLSTATUS) which is only available on GNU Makefile
Currently all corosync dependencies are hardcorded inside the
dlm_controld Makefile. We will determine those dependencies by
pkg-config. This allows us that dlm_controld can detect when the
corosync libaries are installed in a different place determined by
changing the PKG_CONFIG_PATH env
Dave is going to hate me for this, but..
I've been looking over some of the interfaces here, and I'm starting
to very seriously questioning the design decisions of storing the
fsverity hashes in xattrs.
Yes, storing them beyond i_size in the file is a bit of a hack, but
it allows to reuse a lot
