src/lib/libc/sys/open.2, branch release/11.1.0

MFC r318314

2017-05-25T18:55:10+00:00

Add information to open(2) man page about the O_VERIFY flag.

PR:		219262
Reviewed by:	bjk wblock
Approved by:	sjg (mentor)
Obtained from:	Juniper Networks, Inc.

MFC r309026: open(2): Clarify non-POSIX error when opening a symlink with

2016-12-04T15:55:59+00:00

O_NOFOLLOW.

We return [EMLINK] instead of [ELOOP] when trying to open a symlink with
O_NOFOLLOW, so that the original case of [ELOOP] can be distinguished. Code
like cmp -h and xz takes advantage of this.

PR:		214633

Fix markup.

2015-07-07T19:23:59+00:00

MFC after:	1 week
Sponsored by:	The FreeBSD Foundation

Update open(2) to make it more obvious that O_NOCTTY and O_TTY_INIT

2015-04-02T11:41:04+00:00

are ignored.

MFC after:	1 month
Sponsored by:	The FreeBSD Foundation

Document the ERESTART translation to EINTR for devfs nodes.

2013-02-07T15:11:43+00:00

Based on the submission by:	jilles
MFC after:	2 weeks

Fix mdoc errors.

2011-04-01T19:57:27+00:00

Submitted by:	ru
MFC after:	3 days

Document O_CLOEXEC.

2011-03-25T14:01:18+00:00

Reviewed by:	jhb
MFC after:	1 week

Fix typos, spelling, formatting and mdoc mistakes found by Nobuyuki while

2010-08-16T15:18:30+00:00

translating these manual pages.  Minor corrections by me.

Submitted by:	Nobuyuki Koganemaru

Actually make O_DIRECTORY work.

2010-03-21T20:43:23+00:00

According to POSIX open() must return ENOTDIR when the path name does
not refer to a path name. Change vn_open() to respect this flag. This
also simplifies the Linuxolator a bit.

Add missing POSIX 1003.1-2008 open(2) flag; O_TTY_INIT.

2009-02-28T10:10:30+00:00

On FreeBSD, this is the default behaviour. According to the spec, we may
give this flag a value of zero, but I'd rather not do this. If we define
it to a non-zero value, we can always change default behaviour without
changing the ABI. This is very unlikely to happen, though.