[Bug 262440] Order of startup scripts in /etc/rc.d leads to problems with readonly root
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262440] Order of startup scripts in /etc/rc.d leads to problems with readonly root"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262440] Order of startup scripts in /etc/rc.d leads to problems with readonly root"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 262440] Order of startup scripts in /etc/rc.d leads to problems with readonly root"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 09 Mar 2022 09:35:07 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262440 Bug ID: 262440 Summary: Order of startup scripts in /etc/rc.d leads to problems with readonly root Product: Base System Version: 13.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: misc Assignee: bugs@FreeBSD.org Reporter: nkoch@demig.de I am having a system running with readonly root, where tmp is a symlink to /var/tmp which is recreated at every boot with rc.conf settings varmfs="YES" populate_var="YES" This works with 12.1 where var comes before tmp. Under 13.0 tmp comes immediately after mountcritlocal and before var, so I end up in /bin/sh with every boot. Obvious solution would be to add var as a requirement for tmp, but I don't know if that would lead to some other problems. -- You are receiving this mail because: You are the assignee for the bug.