[Bug 233401] Is it safe now to use "mount -t nullfs" instead of mount_nullfs in makefiles (does it return non 0 values reliably on errors)?
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Thu Nov 22 10:29:59 UTC 2018
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233401
Bug ID: 233401
Summary: Is it safe now to use "mount -t nullfs" instead of
mount_nullfs in makefiles (does it return non 0 values
reliably on errors)?
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: bin
Assignee: bugs at FreeBSD.org
Reporter: 0mp at FreeBSD.org
I've stumbled upon the following comment in ports/Mk/bsd.commands.mk[1]:
> # XXX: this is a work-around for an obscure bug where
> # mount -t nullfs returns zero status on errors within
> # a make target
I cannot find a bug report for that. Is this comment still relevant after over
10 years?
[1]:
https://svnweb.freebsd.org/ports/head/Mk/bsd.commands.mk?view=markup&pathrev=462459#l64
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list