From: bernd@petrovitsch.priv.at (Bernd Petrovitsch)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Common signal handler system call
Date: Sat, 19 Mar 2011 22:43:26 +0100 [thread overview]
Message-ID: <1300571006.23326.18.camel@thorin> (raw)
In-Reply-To: <AANLkTin+KxrkgKmcg11+ki8zMgptaZN4j74ga-bCoL=U@mail.gmail.com>
On Sam, 2011-03-19 at 19:48 +0530, mohit verma wrote: [...]
> is there any need of raise() system call if we have kill() system
> call which is capable of sending signals to the process itself?
No there is no need. But at least on Fedora 13, `man 2 raise` doesn't
give anything but `man 3 raise` does. The simple interpretation is that
that raise() is a C library function and not a system call.
Well, you can implement your idea as a library function too.
Apart from the "just for fun" factor or to learn how to implement a new
system call, I see no real gain to move that into kernel.
> Actually there are lots of examples of this type .Some of them are for
> compatibility reasons and still some are "i dont know why." :)
FullACK. The system calls were defined ages ago and who knows now what
and why people (and *who*) defined it, so some cruft should be expected.
And since such design decision tend to live for ages, more people should
throw their thoughts in .....
[...]
Bernd
--
Bernd Petrovitsch Email : bernd at petrovitsch.priv.at
LUGA : http://www.luga.at
next prev parent reply other threads:[~2011-03-19 21:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 19:54 Common signal handler system call mohit verma
2011-03-18 20:02 ` Fwd: " mohit verma
2011-03-18 20:11 ` mohit verma
2011-03-18 20:30 ` Manish Katiyar
2011-03-18 21:12 ` mohit verma
2011-03-19 11:31 ` Bernd Petrovitsch
2011-03-19 14:18 ` mohit verma
2011-03-19 21:43 ` Bernd Petrovitsch [this message]
2011-03-20 7:38 ` mohit verma
2011-03-20 14:57 ` Javier Martinez Canillas
2011-03-21 10:38 ` Bernd Petrovitsch
2011-03-21 12:16 ` mohit verma
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=1300571006.23326.18.camel@thorin \
--to=bernd@petrovitsch.priv.at \
--cc=kernelnewbies@lists.kernelnewbies.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).