From: Luiz Fernando Capitulino <lcapitulino@prefeitura.sp.gov.br>
To: Jesper Juhl <juhl-lkml@dif.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SCO's infringing files list
Date: Tue, 23 Dec 2003 09:18:08 -0200 [thread overview]
Message-ID: <1072178288.8753.7.camel@telecentrolivre> (raw)
In-Reply-To: <Pine.LNX.4.56.0312222353310.27724@jju_lnx.backbone.dif.dk>
Hi Jesper,
Em Seg, 2003-12-22 às 21:01, Jesper Juhl escreveu:
> One thing I noticed.
>
> I'm looking at include/signal.h from linux-0.01 and the definition of the
> signal() function, the prototype in include/signal.h is
>
> void (*signal(int _sig, void (*_func)(int)))(int);
>
> I then take a look in my copy of UNIX Network Programming by W. Richard
> Stevens from 1990, and notice that he on page 46 says this :
>
> "...
> A process specifies how it wants a signal handled by calling the signal
> system call.
>
> #include <signal.h>
>
> int (*signal (int sig, void (*func)(int)))(int);
>
> ..."
>
>
> The return type here is "int" while Linus originally made the return type
> "void". If Linus had copied signal.h from UNIX the return type would have
> been "int"...
Seems to me the Linus version comes from Minix. Its return type is
void too:
http://www.minix-vmd.org/source/std/1.5/include/signal.h
--
Luiz Fernando N. Capitulino
<lcapitulino@prefeitura.sp.gov.br>
<http://www.telecentros.sp.gov.br>
next prev parent reply other threads:[~2003-12-23 11:16 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-22 20:42 Stan Bubrouski
2003-12-22 21:14 ` Joseph Pingenot
2003-12-22 21:23 ` Stan Bubrouski
2003-12-22 21:19 ` Tom Felker
2003-12-22 21:55 ` Linus Torvalds
2003-12-23 0:26 ` jw schultz
2003-12-23 1:17 ` Stan Bubrouski
2003-12-23 9:28 ` Florian Weimer
2003-12-23 9:58 ` Giacomo A. Catenazzi
2003-12-23 12:34 ` Linus Torvalds
2003-12-23 13:17 ` viro
2003-12-23 15:44 ` Giacomo A. Catenazzi
2003-12-23 16:04 ` Mitchell Blank Jr
2003-12-23 16:39 ` Mitchell Blank Jr
2003-12-23 17:25 ` Linus Torvalds
2003-12-23 18:40 ` Charles Cazabon
2003-12-23 18:44 ` viro
2003-12-23 18:45 ` Mitchell Blank Jr
2003-12-23 18:52 ` Matti Aarnio
2003-12-23 19:58 ` Shawn
2003-12-23 20:08 ` Stan Bubrouski
2003-12-23 20:25 ` John Shifflett
2004-01-02 19:45 ` Bill Davidsen
2003-12-23 18:47 ` Steven Cole
2003-12-23 20:06 ` Mitchell Blank Jr
2003-12-23 17:44 ` Mitchell Blank Jr
2003-12-23 17:56 ` Linus Torvalds
2003-12-23 18:12 ` Stan Bubrouski
2003-12-23 18:14 ` Harry McGregor
2003-12-23 18:27 ` Stan Bubrouski
2003-12-23 18:40 ` Disconnect
2003-12-23 18:14 ` Stan Bubrouski
2003-12-23 19:02 ` Stan Bubrouski
2003-12-23 19:06 ` Andries Brouwer
2003-12-23 20:18 ` Stan Bubrouski
2003-12-23 20:21 ` Mitchell Blank Jr
2003-12-23 20:27 ` Linus Torvalds
2003-12-23 23:56 ` [OT] " Thomas Zehetbauer
2003-12-24 0:15 ` Stan Bubrouski
2003-12-23 16:15 ` venom
2003-12-23 15:50 ` Mitchell Blank Jr
2003-12-23 17:07 ` Andries Brouwer
2003-12-22 23:52 ` Erik Andersen
2003-12-22 23:01 ` Jesper Juhl
2003-12-23 11:18 ` Luiz Fernando Capitulino [this message]
2003-12-23 4:50 ` David Schwartz
2003-12-23 15:43 Xose Vazquez Perez
2003-12-23 15:46 jpo234
2003-12-23 18:49 jpo234
2003-12-24 12:19 Norman Diamond
2003-12-24 13:11 ` Jussi Laako
[not found] <no.id>
2003-12-28 7:04 ` Rick Bressler
2003-12-30 14:17 Bruno Haible
2003-12-30 17:27 ` Stan Bubrouski
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=1072178288.8753.7.camel@telecentrolivre \
--to=lcapitulino@prefeitura.sp.gov.br \
--cc=juhl-lkml@dif.dk \
--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
all inboxes | Powered by JetHome®