From: Karel Kulhavy <clock@twibright.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Documentation for /dev/tun
Date: Fri, 27 Jan 2006 10:17:58 +0100 [thread overview]
Message-ID: <20060127091758.GA6646@kestrel> (raw)
In-Reply-To: <Pine.LNX.4.58.0601261543000.15286@twin.jikos.cz>
On Thu, Jan 26, 2006 at 03:44:41PM +0100, Jiri Kosina wrote:
> On Thu, 26 Jan 2006, Karel Kulhavy wrote:
>
> > I have /dev/tun on my system and would like to read documentation about
> > it. Because I already know that /dev/ttyS0 has manual page under man
> > ttyS, I typed man tun No manual entry for tun also info tun No menu item
> > `tun' in node `(dir)Top'. I also tried "tun" and "/dev/tun" at Wikipedia
> > and they have nothing.
>
> Documentation/networking/tuntap.txt
> drivers/net/tun.c is quite easy to read too.
Why is man ttyS present and man tun missing? Is there any rule which says
which devices should have manpage and which not?
CL<
>
> --
> JiKos.
next prev parent reply other threads:[~2006-01-27 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 14:04 Documentation for /dev/tun Karel Kulhavy
2006-01-26 14:44 ` Jiri Kosina
2006-01-27 9:17 ` Karel Kulhavy [this message]
2006-01-27 14:15 ` Erik Mouw
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=20060127091758.GA6646@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