From: Mikael Pettersson <mikpe@csd.uu.se>
To: Shane Helms <shanehelms@eircom.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: is KERNEL developement finished, yet ???
Date: Thu, 5 Dec 2002 15:33:12 +0100 [thread overview]
Message-ID: <15855.25512.31292.187557@harpo.it.uu.se> (raw)
In-Reply-To: <200212051224.50317.shanehelms@eircom.net>
Shane Helms writes:
> But, if you're implying that we can start once again from bottom, and come up
> with something better that unix (which has been opensource, around for long
> while, tested and developed by many as well) I _HIGHLY_ doubt, and disagree.
>...
> I doubt there be any such errors (mistakes) if ANY. but then, i'm not a kernel
> developer, and new to this whole mailing list !!
Signal delivery on the current stack as opposed to a process-global
or per-signal sigaltstack is broken as hell. It messes up user-space
code that uses customised stack management methods.
sigaction() with SA_ONSTACK is unreliable because in reality applications
have linked-in libraries, and those libraries have no standard way of
knowing whether the main application wants SA_ONSTACK or not.
LD_PRELOAD:ing your own sigaction() is also unreliable, because C libs
tend to have internal calls that bypass the external name and go directly
to the internal __libc_sigaction() or whatever it happens to be called.
/Mikael
next prev parent reply other threads:[~2002-12-05 14:25 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 2:00 Ed Vance
2002-12-05 12:24 ` Shane Helms
2002-12-05 12:54 ` Joseph D. Wagner
2002-12-05 13:15 ` Andreas Schwab
2002-12-05 18:07 ` Linus Torvalds
2002-12-05 19:52 ` Shane Helms
2002-12-05 20:03 ` Linus Torvalds
2002-12-05 20:09 ` is KERNEL developement finished, yet ??? (ACLs) Tupshin Harper
2002-12-06 10:38 ` Jakob Oestergaard
2002-12-15 5:29 ` Tracy R Reed
2002-12-07 20:34 ` is KERNEL developement finished, yet ??? Kai Henningsen
2002-12-05 18:09 ` Alan Cox
2002-12-05 17:47 ` yodaiken
2002-12-05 19:08 ` John Bradford
2002-12-06 6:15 ` Joseph D. Wagner
2002-12-06 6:30 ` John Alvord
2002-12-06 9:48 ` Alvaro Lopes
2002-12-07 20:43 ` Kai Henningsen
2002-12-07 20:39 ` Kai Henningsen
2002-12-09 14:08 ` Jesse Pollard
2002-12-10 0:26 ` H. Peter Anvin
2002-12-05 14:33 ` Mikael Pettersson [this message]
[not found] <sdef301b.011@mail-01.med.umich.edu>
2002-12-05 16:36 ` Joseph D. Wagner
2002-12-06 3:29 ` Keith Adamson
[not found] <sdef2367.029@mail-02.med.umich.edu>
2002-12-05 15:17 ` Joseph D. Wagner
2002-12-05 15:38 ` Dave Jones
2002-12-05 15:44 ` Eric Weigle
-- strict thread matches above, loose matches on Subject: below --
2002-12-05 14:58 Nicholas Berry
2002-12-03 13:03 cs driver SANTHOSH K
2002-12-04 15:26 ` is KERNEL developement finished, yet ??? Shane Helms
2002-12-04 17:01 ` Joseph D. Wagner
2002-12-04 18:38 ` Alan Cox
2002-12-04 18:07 ` Richard B. Tilley (Brad)
2002-12-04 18:21 ` Richard B. Johnson
2002-12-04 18:39 ` Erik Andersen
2002-12-05 16:59 ` Bill Davidsen
2002-12-05 0:27 ` jeff millar
2002-12-05 23:55 ` Frank van Maarseveen
2002-12-06 0:24 ` Shane Helms
2002-12-06 3:00 ` jeff millar
2002-12-06 3:36 ` Miles Bader
2002-12-06 8:55 ` Helge Hafting
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=15855.25512.31292.187557@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=linux-kernel@vger.kernel.org \
--cc=shanehelms@eircom.net \
/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®