Date: Fri, 14 Nov 2025 00:54:41 +0000 From: void <void@f-m.fm> To: freebsd-questions@freebsd.org Subject: Re: buildworld in NFS /usr/src/ vs. automount /usr/src path Message-ID: <aRZ90VLtzlAfIJka@int21h> In-Reply-To: <aRZ0EGIMFaOC_RKL@dragon.home.genyosha.net> References: <aRZVvPICgVteWLh6@dragon.home.genyosha.net> <aRZx3S4uvasrY2P1@int21h> <aRZ0EGIMFaOC_RKL@dragon.home.genyosha.net>
index | next in thread | previous in thread | raw e-mail
On Thu, Nov 13, 2025 at 04:13:04PM -0800, Steve Rikli wrote: >Somewhat. My /usr/obj/ today is local to the buildworld's sysdisk so no >NFS is involved in writing to /usr/obj/ -- only /usr/src/ is from NFS, >and it is read-only. > >But some of the notes in the bug make me wonder if moving /usr/obj/ to >NFS, as well as /usr/src/, might somehow produce different results. > >The NFS /usr/obj/ export would have to be writeable, of course, but I'd >prefer to keep /usr/src/ read-only, assuming that's a supported setup >for buildworld. > >That aside, I still wonder about buildworld having some problem with >"/usr/src/" vs. a /usr/src symlink which points to "/net/srv/...". I don't see why /usr/obj or /usr/src over nfs wouldn't be supported I mean the /usr/obj over nfs not working properly is the basis for that ticket after all. I'm not the OP of that PR though. Having /usr/obj /usr/src and /var/cache/ccache over nfs is very useful in situations where the client machine might be low on resources like disk space or have low performance disk media like mmcsd, but might have acceptable network throughput. I think a symlink (particularly a soft link) might produce unexpected results though. The last time I tried that in a buildworld context was many years ago and although I don't remember the exact outcome, I didn't persist with that configuration. --help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aRZ90VLtzlAfIJka>