aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKyle Evans <kevans@FreeBSD.org>2026-02-03 03:21:42 +0000
committerKyle Evans <kevans@FreeBSD.org>2026-04-12 13:43:42 +0000
commitb39cac4b834cee6ab76ebab8ad180a99b1249970 (patch)
tree7fd9bbb073128094a446b2b92640a8dc1eff9c83
parent874d779aa7ddc8216b06e58ff955adf2a54a17d5 (diff)
rc: run the zfs rc script before tmp
The tmp rc script has much the same problem that the var does: it wants to test if /tmp is writable, and mount a tmpfs if it's not. This means that we actually want our zfs datasets mounted first, because we might have a /tmp dataset that changes the story. The ordering problem is particularly noticable with a r/o zfs root, since the write test will fail and we'll mount a tmpfs that later gets covered by our /tmp dataset. If that /tmp dataset inherited readonly, then we're still in trouble. This also fixes `tmpmfs=yes`, which would again get covered by a zfs dataset with the existing ordering. Reviewed by: des (cherry picked from commit d3f21856aa72c28408660ed40ce76bbd0716a991)
-rwxr-xr-xlibexec/rc/rc.d/zfs2
1 files changed, 1 insertions, 1 deletions
diff --git a/libexec/rc/rc.d/zfs b/libexec/rc/rc.d/zfs
index 1e887c67f804..95a5b4774a20 100755
--- a/libexec/rc/rc.d/zfs
+++ b/libexec/rc/rc.d/zfs
@@ -4,7 +4,7 @@
# PROVIDE: zfs
# REQUIRE: zfsbe
-# BEFORE: FILESYSTEMS var
+# BEFORE: FILESYSTEMS tmp var
. /etc/rc.subr