From: "Cygwin Linux Man Pages Maintainer" <Brian.Inglis@SystematicSW.ab.ca>
To: "Cygwin Announcements" <cygwin-announce@cygwin.com>
Subject: Updated: man-pages-linux 6.01
Date: Sat, 22 Oct 2022 13:40:41 -0600 [thread overview]
Message-ID: <20221022134041.25134-1-Brian.Inglis@SystematicSW.ab.ca> (raw)
The following package has been upgraded in the Cygwin distribution:
* man-pages-linux 6.01
Documents the Linux kernel system calls and C library interfaces used
by programs, plus system and administrative utilities, devices, file
system, file, and data formats, and related information.
For more information, see the project home page:
https://kernel.org/doc/man-pages/
You may also search and read the pages online:
https://man7.org/linux/man-pages/
although the latest release may not yet be available.
Release 6 added some section 2 and 3 pages suffixed by const, head,
or type installed in the base section directory.
As Cygwin has its own man pages with some conflicts, these man pages
are installed under /usr/share/man/linux/, so by default searching
or viewing these pages requires the option:
$ apropos -m|--systems linux ...
$ man -m|--systems linux ...
Cygwin man pages are under the default system "man", so for convenience
both systems may be specified separated by comma e.g.
$ man -m man,linux ...
The path or option may also be added explicitly to a users MANPATH or
alias e.g.
$ export MANPATH=$MANPATH:/usr/share/man/linux
$ alias apropos='apropos -m man,linux'
$ alias man='man -m man,linux'
Add -a to show both Cygwin and Linux manual pages if present, or swap
the order to prioritize Linux.
For recent changes, please see below, or after installation read
/usr/share/doc/man-pages-linux/CHANGES:
man-pages-6.01 2022-10-18
Global changes
* Manual pages' sections:
- Title (.TH):
- Remove the hardcoded date (TH 3rd argument), and replace it by a
placeholder that should be changed when creating the tarball.
This removes the need for a tstamp commit before each release.
* Build system:
- Update manual page dates (TH 3rd argument) when creating the tarball
with 'make dist'. this removes the need for a tstamp commit before
each release.
- Don't print spurious errors from the Makefile that are not relevant.
Changes to individual pages
The manual pages (and other files in the repository) have been improved
beyond what this changelog covers.
New and rewritten pages
* EOF.3const
Newly documented interfaces in existing pages
* fanotify_mark.2
FAN_MARK_IGNORE
* open.2, statx.2
STATX_DIOALIGN
* feature_test_macros.7
_FORTIFY_SOURCE=3
_TIME_BITS
reply other threads:[~2022-10-22 19:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221022134041.25134-1-Brian.Inglis@SystematicSW.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-announce@cygwin.com \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).