From: Karel Kulhavy <clock@twibright.com>
To: linux-kernel@vger.kernel.org
Subject: Kernel manual pages
Date: Fri, 27 Jan 2006 10:26:23 +0100 [thread overview]
Message-ID: <20060127092623.GA7882@kestrel> (raw)
Who is responsible for writing the linux kernel manual pages? I went to
vger.kernel.org and there is "There is much information about Linux on
the web." which points to 7 different 3rd party websites. I searched
for "manual" and "manpage" in all 7 and didn't find any mention of
manual pages.
I also suggest the http://kernel.org/links.html to be structured
according to topic, and not according to name of the website. Because
if the user comes, he mostly needs to know information about particular
topic. This way he doesn't know which link to click to obtain the
information.
Furthermore I suggest "Manuals" section to be added to vger.kernel.org
in the style OpenBSD has:
http://openbsd.org/
http://www.openbsd.org/cgi-bin/man.cgi
CL<
next reply other threads:[~2006-01-27 9:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-27 9:26 Karel Kulhavy [this message]
2006-01-27 14:30 ` Kernel manual pages Erik Mouw
2006-04-30 14:11 ` Karel Kulhavy
[not found] ` <20060127093103.4f196745.seanlkml@sympatico.ca>
2006-01-27 14:31 ` sean
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=20060127092623.GA7882@kestrel \
--to=clock@twibright.com \
--cc=linux-kernel@vger.kernel.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