- adjust references
- remove stray comments, streamline description
(charsets(7) and Wikipedia provide more detailed
and up-to-date description)
- cosmetics
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
- adjust references
- remove stray comments, streamline description
(charsets(7) and Wikipedia provide more detailed
and up-to-date description)
- cosmetics
- adjust references
- remove stray comments, streamline description
(charsets(7) and Wikipedia provide more detailed
and up-to-date description)
- list differences between koi8-r.7 vs koi8-u.7
- cosmetics
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
- adjust references
- remove stray comments, streamline description
(charsets(7) and Wikipedia provide more detailed
and up-to-date description)
- list differences between koi8-r.7 vs koi8-u.7
- cosmetics
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This and the follow-up patches will provide unification of
charset pages, minor cleanups, and some unifying cosmetic
changes. References are adjusted so that all pages include
a reference to charsets(7), which contains a description of
these sets, stray comments are removed, some obsolete
statements (like ISO 8859-1 being the de-facto ASCII
replacement) are removed, and some minor reformatting
to minimize diff's between the pages are done.
The actual substance, the character tables, remain unchanged.
This series changes the following pages (under man7): ascii,
armscii, cp1251, koi8-r, koi8-u, and all of iso_8859-*.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
CP 1252 is probably one of the most used Windows Code Pages so
let's add a page for it alongside with the already provided
CP 1251 page.
Table generated from /usr/share/i18n/charmaps/CP1252.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This patch adds a short description about the contents of
/proc/buddyinfo and how this file can be used to assist
in checking for memory fragmentation issues.
Signed-off-by: Elie De Brauwer <eliedebrauwer@gmail.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The text "Each of these calls sets errno to an appropriate
value in the case of an error." is not only for waitid.
This patch adds a paragraph break to move the errno note
to a new paragraph where it makes sense, as it applies to
all the wait* functions.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
The default values of SHMALL and SHMMAX have been increased.
Signed-off-by: Manfred Spraul <manfred@colorfullife.com>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
See https://bugzilla.kernel.org/show_bug.cgi?id=84701
As noted by C. Alex North-Keys:
1) Command name extensions considered harmful: Adding ".sh", or
any other unneeded extension, unnecessarily duplicates meta
information already present in the interpreter directive,
exposing an implementation detail that then ends up explicitly
part of other programs running this one. Later, when such a
script is replaced with a new version in Python, C, etc., the
useless ".sh" has to be retained to avoid breaking those other
programs' calls to this one, and now has a stark antifunction
of lying about the script's content and occasionally causing
admins to run undefined experiments as root (like
"bash -x ./reallyperlscript.sh"). Such extensions, while fine
in DOS which ignores extensions explicitly, is a serious flaw
in Unix-targeted script writing. Canonical documentation
from the Linux manual should not support such a flawed idiom -
recommending against it would be preferred.
A more extensive rant against them can be found at:
http://www.talisman.org/~erlkonig/documents/commandname-extensions-considered-harmful
2) The space after "#!" in the interpreter directive is minor -
and the kernel's fs/binfmt_script.c specifically allows for it -
but versions of unix have length limits from ~30 characters to
Linux's 127 or so (if that number's correct) so the space does
have a cost. Most scripts I've seen lack that space, and
there's no real reason to encourage it.
Reported-by: C. Alex North-Keys <erlkonig@talisman.org>
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
CLONE_NEWIPC is the correct constant, as can be seen in the detailed
list of namespaces & their corresponding constants, as well as the
clone(2) man page and include/uapi/linux/sched.h in the Linux source tree.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
It's possible to get ENOENT returned from getgrent()
if the backend, for example say SSSD, isn't configured
or the daemon isn't running. The same can be said of any
of the NSS backend.
As POSIX does not list ENOENT, we can list it ourselves
and define it how we like.
I don't know how you handle errno values that are glibc
specific, but here is the patch that enhances getgrent(3)
to make users aware of what ENOENT is intended to mean
from glibc.
While I'm fixing one I might as well [add EAGAIN].
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Marko Myllynen