From: "H. Peter Anvin" <hpa@zytor.com>
To: Ned Ulbricht <nedu@netscape.net>,
"Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Greg KH <gregkh@linuxfoundation.org>,
"Theodore Ts'o" <tytso@mit.edu>,
Maarten Brock <Maarten.Brock@sttls.nl>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: RFC: Serial port DTR/RTS - O_<something>
Date: Sat, 15 Nov 2025 16:47:37 -0800 [thread overview]
Message-ID: <2846db90-fb05-41d2-b8de-c678af75a04b@zytor.com> (raw)
In-Reply-To: <6c26eea2-6f90-f48a-9488-e7480f086c70@netscape.net>
On 2025-11-15 13:29, Ned Ulbricht wrote:
> |
> | O_TTY_INIT
>
> https://pubs.opengroup.org/onlinepubs/9799919799/
>
> That's what motivates my first-glance preference to name this new flag,
> which will have approximately opposite behavior, as O_TTY_NOINIT.
>
> But as a generic abstraction, I more prefer O_KEEP.
>
O_KEEP seems a little vague, but O_KEEPCONFIG seems like a decent name.
It seems like we don't have several new flags:
O_EXEC
O_SEARCH
O_CLOFORK
O_TTY_INIT
O_RSYNC
O_NOCLOBBER
Some of them *may* be possible to construct with existing Linux options, I'm
not 100% sure; in particular O_SEARCH might be the same as (O_DIRECTORY|O_PATH).
O_NOCLOBBER looks like an odd in-between between O_EXCL and
(O_EXCL|O_NOFOLLOW); stated to be specifically to implement the shell
"noclobber" semantic.
-hpa
next prev parent reply other threads:[~2025-11-16 0:47 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 7:53 RFC: Serial port DTR/RTS - O_NRESETDEV H. Peter Anvin
2025-11-07 17:37 ` Theodore Ts'o
2025-11-09 2:25 ` H. Peter Anvin
2025-11-10 3:35 ` Theodore Ts'o
2025-11-10 5:00 ` H. Peter Anvin
2025-11-10 10:06 ` Maarten Brock
2025-11-10 20:19 ` Theodore Ts'o
2025-11-10 21:05 ` H. Peter Anvin
2025-11-11 3:51 ` Theodore Ts'o
2025-11-11 3:57 ` H. Peter Anvin
2025-11-11 4:38 ` Theodore Ts'o
2025-11-11 10:21 ` Maarten Brock
2025-11-11 21:28 ` H. Peter Anvin
2025-11-12 11:22 ` Greg KH
2025-11-12 16:09 ` H. Peter Anvin
2025-11-12 16:46 ` Greg KH
2025-11-12 19:12 ` H. Peter Anvin
2025-11-12 19:39 ` Greg KH
2025-11-12 19:53 ` H. Peter Anvin
2025-11-12 19:55 ` H. Peter Anvin
2025-11-13 22:24 ` RFC: Serial port DTR/RTS - O_<something> H. Peter Anvin
2025-11-14 10:26 ` Maarten Brock
2025-11-14 18:49 ` Maciej W. Rozycki
2025-11-14 18:53 ` H. Peter Anvin
2025-11-15 21:29 ` Ned Ulbricht
2025-11-15 22:29 ` H. Peter Anvin
2025-11-16 0:47 ` H. Peter Anvin [this message]
2025-11-18 16:33 ` Ned Ulbricht
2025-11-18 17:31 ` H. Peter Anvin
2025-11-18 18:05 ` H. Peter Anvin
2025-11-20 13:31 ` Ned Ulbricht
2025-11-10 5:20 ` RFC: Serial port DTR/RTS - O_NRESETDEV H. Peter Anvin
2025-11-09 20:43 ` Maciej W. Rozycki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2846db90-fb05-41d2-b8de-c678af75a04b@zytor.com \
--to=hpa@zytor.com \
--cc=Maarten.Brock@sttls.nl \
--cc=gregkh@linuxfoundation.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=nedu@netscape.net \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®