From 9b33ec13e6024a13760c051580a81bb31e2a60a9 Mon Sep 17 00:00:00 2001 From: Antonio SJ Musumeci Date: Sun, 30 Nov 2025 23:29:29 -0600 Subject: [PATCH] technical_behavior_and_limitations.md --- .../docs/faq/technical_behavior_and_limitations.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/mkdocs/docs/faq/technical_behavior_and_limitations.md b/mkdocs/docs/faq/technical_behavior_and_limitations.md index f5b4eac6..099f5303 100644 --- a/mkdocs/docs/faq/technical_behavior_and_limitations.md +++ b/mkdocs/docs/faq/technical_behavior_and_limitations.md @@ -273,21 +273,22 @@ practice. The alternative to this strategy is to create a setup where a filesystem proxy of sorts is spawned for each uid:gid combination needed and the main mergerfs process makes requests to those proxies to do the work needed. The problem is that that kind of setup is both -more complex and slower. +more complex and slower. If it is found that the current strategy +causes issues the more complex one will be reconsidered. +As a result of this change it is now necessary for the FUSE +`default_permissions` feature be used for proper entitlements +management. mergerfs does allow it to be disabled but it should only +be done so for debugging purposes. ## Does mergerfs support idmap? -Yes. At least in so far as it's been enabled now the FUSE itself -allows a filesystem to indicate it is allowed. - +Yes. Requires that [kernel-permissions-check](../config/kernel-permissions-check.md) be enabled (the default.) -If there are any usage issues contact the [author](../support.md). - ## What happens if a branch filesystem blocks?