Age | Commit message (Collapse) | Author |
|
getopt(3) returns '?' when it encounters a flag not present in the in
the optstring or if a flag is missing its option argument. We can
handle this case with the "default" failure case with no loss of
legibility. Hence, remove all the redundant "case '?':" lines.
Prompted by dlg@. With help from dlg@ and millert@.
Link: https://marc.info/?l=openbsd-tech&m=167011979726449&w=2
ok naddy@ millert@ dlg@
|
|
|
|
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.
|
|
NetBSD 1.0A was not a release, but it was
what would be called NetBSD 1.0-current in OpenBSD terminology,
see http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/conf/newvers.sh#rev1.17
patch from Sevan Janiyan <venture37 at geeklan dot co dot uk>
|
|
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
|
|
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
|
|
|
|
possible. Annotate <sys/param.h> lines with their current reasons. Switch
to PATH_MAX, NGROUPS_MAX, HOST_NAME_MAX+1, LOGIN_NAME_MAX, etc. Change
MIN() and MAX() to local definitions of MINIMUM() and MAXIMUM() where
sensible to avoid pulling in the pollution. These are the files confirmed
through binary verification.
ok guenther, millert, doug (helped with the verification protocol)
|
|
|
|
unmaintainable). these days, people use source. these id's do not provide
any benefit, and do hurt the small install media
(the 33,000 line diff is essentially mechanical)
ok with the idea millert, ok dms
|
|
|
|
systems, okay thib@ ian@ millert@ beck@
|
|
argument "resolved", since it is undefined.
ok and help millert, otto
|
|
also fixes pr1662. from otto moerbeek
|
|
to a partition in the disklabel.
suggested by Phil Pennock.
ok krw@ millert@
|
|
|
|
o document EROFS in man page (2 possible causes)
o recognize EROFS in mount_ffs and try to give a reasonable error message
deraadt@ OK
|
|
rescinded 22 July 1999. Proofed by myself and Theo.
|
|
ok jmc@ millert@
|
|
Remove unmount(2) per millert suggestion; millert@ ok.
|
|
Synch files that use that field.
(This argument is an internal interface specific to OpenBSD, so it won't
cause compatibility problems.)
(No bump, not an ABI change).
ok art, millert...
|
|
hand editing to make comments line up correctly. Another pass is forthcoming that handles the cases that could not be done automatically.
|
|
mpech@prosoft.org.lv
|
|
and otherwise are disabled.
art@ ok.
|
|
|
|
|
|
with soft-updates, but will leak free blocks. On non-softupdates filesystems
this option is strongly unrecommended. It also allows downgrades to readonly
by revoking files opened for writing. If the filesystem have mmap'ed files
writeable this is dangerous. Thus, we do *not* recommend its use!
|
|
|
|
done later.. contact me if you want to help)
|
|
|
|
is used instead; kwesterback@home.com
|
|
|
|
|
|
|
|
|
|
device" (EOPNOTSUPP) so the real problem is obvious. Idea from Peter Seebach
<seebs@taniemarie.solon.com>.
|
|
we can use NLS for the text, not a hardcode English message.
|
|
|
|
|
|
|
|
Removed extraneous text; From Mike Long <mike.long@analog.com>
|
|
|
|
|