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)?
Summary: Is it safe now to use "mount -t nullfs" instead of mount_nullfs in makefiles ...
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-22 10:29 UTC by Mateusz Piotrowski
Modified: 2020-11-02 09:01 UTC (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mateusz Piotrowski freebsd_committer freebsd_triage 2018-11-22 10:29:57 UTC 
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
Comment 1 Mateusz Piotrowski freebsd_committer freebsd_triage 2020-11-02 09:01:02 UTC 
trasz@, you've done some work recently on nullfs. Could it be related?