From: "Michael Kerrisk" <mtk-lkml@gmx.net>
To: Andi Kleen <ak@muc.de>
Cc: rick.jones2@hp.com, netdev@oss.sgi.com
Subject: Re: is UDP_CORK "real"
Date: Wed, 27 Apr 2005 10:20:28 +0200 (MEST) [thread overview]
Message-ID: <16241.1114590028@www42.gmx.net> (raw)
In-Reply-To: m1u0lty7uh.fsf@muc.de
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 1621 bytes --]
> Rick Jones <rick.jones2@hp.com> writes:
> > today? While man tcp described TCP_CORK, on the two places I've
> > checked thusfar, man udp does not describe UDP_CORK. I'm not sure if
> > that means UDP_CORK is "unreal" or just that the udp manpage needs
> > repair (or was out of date on my systems).
>
> AFAIK nobody has been updating the protocol manpages since I stopped
> doing so several years ago when they were included into the
> standard manpages. There are lots of missing features
> etc. that could be documented, the BUGS sections are usually
> out of date etc. It is roughly at the state of early 2.3.
I make ocassional changes, as far as my knowledge permits.
But there's lots that I don't know...
> There is also unfortunately no policy to require a manpage
> update when a new feature is added to the kernel.
Yes, unfortunately.
> Some manpages have been even never fully written like the ipv6 manpage.
> Perhaps someone is interested in updating all these? It unfortunately
> needs quite a lot of RTFS to figure out what the code actually does.
I welcome all such patches, which will go into the
standard man-pages set (get the latest set at
ftp://ftp.win.tue.nl/pub/linux-local/manpages/ ).
Please send patches to: mtk-manpages@gmx.net
In terms of checking people's input, it helps if you identify
how the knowledge going into a patch was obtained, and perhaps
point me at some relevant parts of the source.
Cheers,
Michael
--
+++ GMX - die erste Adresse für Mail, Message, More +++
10 GB Mailbox, 100 FreeSMS http://www.gmx.net/de/go/topmail
next prev parent reply other threads:[~2005-04-27 8:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 23:14 is UDP_CORK "real" Rick Jones
2005-04-21 23:25 ` David S. Miller
2005-04-21 23:53 ` Rick Jones
2005-04-26 13:40 ` Andi Kleen
2005-04-27 8:20 ` Michael Kerrisk [this message]
[not found] ` <426F2A1D.10001@aarnet.edu.au>
2005-04-27 12:26 ` network manpages was " Andi Kleen
2005-04-27 18:43 ` David S. Miller
2005-04-29 15:29 ` Andi Kleen
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=16241.1114590028@www42.gmx.net \
--to=mtk-lkml@gmx.net \
--cc=ak@muc.de \
--cc=netdev@oss.sgi.com \
--cc=rick.jones2@hp.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 NNTP newsgroup(s).