From: Kurt Wall <kwall@kurtwerks.com>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: syscall __NR_mmap2
Date: Tue, 8 Jul 2003 10:51:43 -0400 [thread overview]
Message-ID: <20030708145143.GY16938@kurtwerks.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0307081033190.267@chaos>
Quoth Richard B. Johnson:
[...]
> Yeah? So the Linux kernel now requires a specific vendor distribution?
> Since when?
I don't think this vendor specific. The mmap2() man page I have comes
from the man pages package maintained by Andries Brouwer (release 1.56).
The LSM file says you can get them at
ftp://ftp.win.tue.nl/pub/linux-local/manpages
> So, to get the proper documentation of the Linux Kernel, I now
> need to purchase a vendor's distribution??? I think not. I think
No.
> the sys-calls need to be documented and I think that I have established
> proof of that supposition.
>
> Script started on Tue Jul 8 10:35:05 2003
> # man mmap2
> No manual entry for mmap2
> # mmap
> # man map
>
> MMAP(2) Linux Programmer's Manual MMAP(2)
>
> NAME
> mmap, munmap - map or unmap files or devices into memory
>
> SYNOPSIS
> #include <sys/types.h>
> #include <sys/mman.h>
>
> caddr_t mmap(caddr_t addr, size_t len, int prot , int
> flags, int fd, off_t offset );
> int munmap(caddr_t addr, size_t len);
>
> DESCRIPTION
> WARNING: This is a BSD man page. Linux 0.99.11 can't map
> files, and can't do other things documented here.
I'd say your man pages are woefully out of date.
Kurt
--
Do infants have as much fun in infancy as adults do in adultery?
prev parent reply other threads:[~2003-07-08 14:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-07 21:00 syscall __NR_mmap2 Richard B. Johnson
2003-07-07 21:32 ` Ulrich Drepper
2003-07-08 11:56 ` Richard B. Johnson
2003-07-08 0:36 ` Jamie Lokier
2003-07-08 11:54 ` Richard B. Johnson
2003-07-08 13:59 ` Kurt Wall
2003-07-08 14:05 ` Jamie Lokier
2003-07-08 14:40 ` Richard B. Johnson
2003-07-08 14:49 ` Randy.Dunlap
2003-07-08 14:51 ` Kurt Wall [this message]
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=20030708145143.GY16938@kurtwerks.com \
--to=kwall@kurtwerks.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;
as well as URLs for NNTP newsgroup(s).