Date: Thu, 22 Nov 2018 10:29:57 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [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)? Message-ID: <bug-233401-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D233401 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@FreeBSD.org Reporter: 0mp@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 o= ver 10 years? [1]: https://svnweb.freebsd.org/ports/head/Mk/bsd.commands.mk?view=3Dmarkup&path= rev=3D462459#l64 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-233401-227>