public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andries Brouwer <aeb@veritas.com>
To: linux-kernel@vger.kernel.org
Cc: ahu@ds9a.nl, goemon@anime.net
Subject: Re: 2.4 sendfile() not doing as manpage promises?
Date: Sun, 19 Nov 2000 17:36:23 +0100	[thread overview]
Message-ID: <20001119173623.A1185@veritas.com> (raw)
In-Reply-To: <20001119001558.B10579@home.ds9a.nl> <Pine.LNX.4.30.0011181513290.5897-100000@anime.net> <20001119015259.A10773@home.ds9a.nl>
In-Reply-To: <20001119015259.A10773@home.ds9a.nl>; from ahu@ds9a.nl on Sun, Nov 19, 2000 at 01:53:00AM +0100

On Sun, Nov 19, 2000 at 01:53:00AM +0100, bert hubert wrote:
:  On Sat, Nov 18, 2000 at 03:15:28PM -0800, Dan Hollis wrote:
:  
:::  In that case, the wording of the manpage needs to be changed, as it
:::  implies that 'either or both' of the filedescriptors can be sockets.
::  
::  Its quite clear.
::  
::  DESCRIPTION
::         This  call copies data between file descriptor and another
::         file  descriptor  or  socket.   in_fd  should  be  a  file
::         descriptor   opened  for  reading.   out_fd  should  be  a
::         descriptor opened for writing or a connected socket.
::  
::  in_fd must be a file, out_fd can be a file or socket.
:  
:  My manpages must be outdated then, my manpage is from 1 Dec 1998. Thanks for
:  the correction.

The manpage is dated 1 Dec 1998 and reads

DESCRIPTION
       This call copies data  between  one  file  descriptor  and
       another.   Either  or  both  of these file descriptors may
       refer to a socket.  in_fd  should  be  a  file  descriptor
       opened  for  reading  and  out_fd  should  be a descriptor
       opened for writing.

If that is incorrect, then editing a private copy of the manpage,
as Dan Hollis, or the distributor from whom he got his page,
seems to have done, does not suffice to change the manpage distribution.

(Moreover, the text Dan Hollis quotes is rather strange --
also sockets give one a file descriptor, so the author
of that modified man page did not know what he was talking
about, or was not being precise.)

Andries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-19 17:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-18 23:15 2.4 sendfile() not doing as manpage promises? bert hubert
2000-11-18 23:15 ` Dan Hollis
2000-11-19  0:53   ` bert hubert
2000-11-19 16:36     ` Andries Brouwer [this message]
2000-11-19 23:16       ` bert hubert
2000-11-20  1:11       ` Dan Hollis

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=20001119173623.A1185@veritas.com \
    --to=aeb@veritas.com \
    --cc=ahu@ds9a.nl \
    --cc=goemon@anime.net \
    --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