diff options
author | Alejandro Colomar <alx.manpages@gmail.com> | 2022-09-09 14:15:08 +0200 |
---|---|---|
committer | Alejandro Colomar <alx.manpages@gmail.com> | 2022-09-09 14:15:08 +0200 |
commit | 96e72ec1fbadd13cbcbc2b263540e4f5e9e09d7c (patch) | |
tree | 70686b943e33a6e939ad265acb7ddfef70b91f32 /man2type | |
parent | 8f4ed6463206e8ede815c72085c7305dafc2e4fc (diff) |
Revert "src.mk, All pages: Move man* to man/"
This reverts commit 70ac1c4785fc1e158ab2349a962dba2526bf4fbc.
Link: <https://lore.kernel.org/linux-man/YxcV4h+Xn7cd6+q2@pevik/T/>
Reported-by: Petr Vorel <pvorel@suse.cz>
Reported-by: Jakub Wilk <jwilk@jwilk.net>
Cc: Stefan Puiu <stefan.puiu@gmail.com>
Signed-off-by: Alex Colomar <alx.manpages@gmail.com>
Diffstat (limited to 'man2type')
-rw-r--r-- | man2type/open_how.2type | 51 |
1 files changed, 51 insertions, 0 deletions
diff --git a/man2type/open_how.2type b/man2type/open_how.2type new file mode 100644 index 000000000..92838d69d --- /dev/null +++ b/man2type/open_how.2type @@ -0,0 +1,51 @@ +.\" Copyright (c) 2022 by Alejandro Colomar <colomar.6.4.3@gmail.com> +.\" +.\" SPDX-License-Identifier: Linux-man-pages-copyleft +.\" +.\" +.TH OPEN_HOW 2type 2022-06-16 "Linux man-pages (unreleased)" +.SH NAME +open_how \- how to open a pathname +.SH LIBRARY +Linux kernel headers +.SH SYNOPSIS +.EX +.B #include <linux/openat2.h> +.PP +.B struct open_how { +.BR " u64 flags;" " /* " O_ "* flags */" +.BR " u64 mode;" " /* Mode for " O_ { CREAT , TMPFILE "} */" +.BR " u64 resolve;" " /* " RESOLVE_ "* flags */" + /* ... */ +.B }; +.EE +.SH DESCRIPTION +Specifies how a pathname should be open. +.PP +The fields are as follows: +.TP +.I flags +This field specifies the file creation and file status flags +to use when opening the file. +.TP +.I mode +This field specifies the mode for the new file. +.TP +.I resolve +This is a bit mask of flags that modify the way in which +.I all +components of a pathname will be resolved +(see +.BR path_resolution (7) +for background information). +.SH VERSIONS +Extra fields may be appended to the structure, +with a zero value in a new field resulting in +the kernel behaving as though that extension field was not present. +Therefore, a user +.I must +zero-fill this structure on initialization. +.SH STANDARDS +This type is Linux-specific. +.SH SEE ALSO +.BR openat2 (2) |