From: "Theodore Ts'o" <tytso@mit.edu>
To: Larry McVoy <lm@mcvoy.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Project Idea: The UNIX Programmer's Manual: Heritage Edition
Date: Thu, 21 Sep 2023 09:37:00 -0400 [thread overview]
Message-ID: <ZQxG_L1GsW_lSM6i@mit.edu> (raw)
In-Reply-To: <20230920195635.GG28844@mcvoy.com>
On Wed, Sep 20, 2023 at 12:56:35PM -0700, Larry McVoy wrote:
> On Tue, Sep 19, 2023 at 07:25:13PM -0700, Adam Thornton wrote:
> > Yeah, I'm less angry at GNU now--I didn't search as hard, but when I found
> > out 4.3BSD didn't have HISTORY (and neither does 2.11BSD, which is still
> > actively-ish maintained) then I figured it wasn't something classical that
> > GNU dropped, just never imported. I feel like it existed on SunOS and
> > Solaris but I might be wrong about that? Was it really FreeBSD that
> > introduced it?
>
> I don't think SunOS had it. The SunOS man pages were pretty terse, the
> powers that be wanted just the facts. I remember get beat up for putting
> examples in some of the man pages I wrote, they got taken out "because
> examples are for user guides, man pages are not user guides, they are a
> reference guide" or something like that.
These days, I find the much more useful sections are VERSIONS and
STANDARDS, e.g.:
VERSIONS
openat() was added in Linux 2.6.16; library support was added
in glibc 2.4.
STANDARDS
open(), creat() SVr4, 4.3BSD, POSIX.1‐2001, POSIX.1‐2008.
openat(): POSIX.1‐2008.
openat2(2) is Linux‐specific.
The O_DIRECT, O_NOATIME, O_PATH, and O_TMPFILE flags are
Linux‐specific. One must define _GNU_SOURCE to obtain their
definitions.
The O_CLOEXEC, O_DIRECTORY, and O_NOFOLLOW flags are not
specified in POSIX.1‐2001, but are specified in POSIX.1‐2008.
Since glibc 2.12, one can obtain their definitions by defining
either _POSIX_C_SOURCE with a value greater than or equal to
200809L or _XOPEN_SOURCE with a value greater than or equal to
700. In glibc 2.11 and earlier, one obtains the definitions by
defining _GNU_SOURCE.
As noted in feature_test_macros(7), feature test macros such as
_POSIX_C_SOURCE, _XOPEN_SOURCE, and _GNU_SOURCE must be defined
before including any header files.
- Ted
next prev parent reply other threads:[~2023-09-21 13:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 20:32 [TUHS] " segaloco via TUHS
2023-09-19 23:39 ` [TUHS] " Larry McVoy
2023-09-20 1:26 ` segaloco via TUHS
2023-09-20 1:30 ` segaloco via TUHS
2023-09-20 14:57 ` Warner Losh
2023-09-20 15:40 ` Dan Cross
2023-09-20 2:09 ` Clem Cole
2023-09-20 2:25 ` Adam Thornton
2023-09-20 2:50 ` segaloco via TUHS
2023-09-20 19:56 ` Larry McVoy
2023-09-20 20:52 ` segaloco via TUHS
2023-09-20 22:31 ` Dave Horsfall
2023-09-21 4:09 ` Wesley Parish
2023-09-21 13:08 ` John P. Linderman
2023-09-21 0:26 ` Marc Donner
2023-09-21 3:06 ` Adam Thornton
2023-09-21 3:30 ` G. Branden Robinson
2023-09-21 3:48 ` Phil Budne
2023-09-21 13:37 ` Theodore Ts'o [this message]
2023-09-20 21:15 ` Alan Coopersmith
2023-09-21 3:49 ` G. Branden Robinson
2023-09-19 23:43 ` Adam Thornton
2023-09-20 13:23 ` Chet Ramey
2023-09-20 14:12 ` Alejandro Colomar (man-pages)
2023-09-19 23:47 ` KenUnix
2023-09-20 6:16 ` Jeremy C. Reed
2023-09-20 7:19 ` markus schnalke
2023-09-21 15:53 ` Kenneth Goodwin
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=ZQxG_L1GsW_lSM6i@mit.edu \
--to=tytso@mit.edu \
--cc=lm@mcvoy.com \
--cc=tuhs@tuhs.org \
/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;
as well as URLs for NNTP newsgroup(s).