wireguard-openbsd/sbin/mount/mount.c, branch jd/queueboosts

Adapt to POSIX realpath(3); if it returns NULL, use the mount path as-is.

2019-07-19T15:13:17Z

Fixes an inability to mount via diskuid. Also use mntpath, not *argv, on error for more accurate messages. OK martijn@ mlarkin@

When system calls indicate an error they return -1, not some arbitrary

2019-06-28T13:32:41Z

value < 0. errno is only updated in this case. Change all (most?) callers of syscalls to follow this better, and let's see if this strictness helps us in the future.

Postpone pledge call until after the getopt switch and hoist the call to

2017-02-06T17:15:56Z

readlabelfs over it. This avoids a pledge abort due to the fact that the ioctl DIOCGDINFO may not be allowed on the given file: mount /dev/tty /tmp. ok benno

Some simple cleanup:

2017-01-25T02:33:25Z

* check strdup for malloc failure * remove obvious /* NOTREACHED */ * return instead of exit from main * err(1, NULL) instead of err(1, "malloc") * mark usage as __dead ok deraadt

whitespace

2017-01-24T23:41:44Z

Add a noperm mount flag for FFS to be used for building release sets

2016-09-10T16:53:30Z

without root privileges. This is only the kernel/mount flag; additional work in the build Makefile's will be necessary such that the files in $DESTDIR are created with correct permissions. tedu couldn't find anything wrong with it in a quick review idea & ok deraadt

strlen + malloc + snprintf == asprintf

2016-09-04T19:45:27Z

ok martijn@ deraadt@

somebody forgot to look at format string warnings

2016-06-26T19:53:40Z

Add a bit more verbosity to tmpfs mount(8) output.

2016-06-20T08:36:36Z

ok millert@ feedback/ok natano@

W^X violations are no longer permitted by default. A kernel log message

2016-05-27T19:45:04Z

is generated, and mprotect/mmap return ENOTSUP. If the sysctl(8) flag kern.wxabort is set then a SIGABRT occurs instead, for gdb use or coredump creation. W^X violating programs can be permitted on a ffs/nfs filesystem-basis, using the "wxallowed" mount option. One day far in the future upstream software developers will understand that W^X violations are a tremendously risky practice and that style of programming will be banished outright. Until then, we recommend most users need to use the wxallowed option on their /usr/local filesystem. At least your other filesystems don't permit such programs. ok jca kettenis mlarkin natano