[lkml]   [1998]   [Sep]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Interesting scheduling times
 > >> I don't trust him either. Among other things, he changed signal()
> >> behavior. Gee, thanks for breaking all the apps with SysV expectations.
> >
> > Any program that counts on the behavior of signal() in this manner
> > is broken and should itself be patched to use sigaction or to be
> > more robust in any of several ways.
> No. The behavior was well-defined on Linux until Drepper broke it.

Any program that counts on the behavior of signal() in this manner is
broken. What part of that isn't clear? Whether it was always this way
on Linux (and I'm not as certain of that as you are) is completely

> > In my opinion, the BSD behavior is far more useful than the
> > sysv behavior, and glibc has this particular issue right.
> The BSD behavior is totally useless, since it can not be assumed.

It can be checked for in a configure script. The NetKit configure
scripts, which are hardly amazingly sophisticated, managed this
without any trouble.

> [useless flamage deleted]

This is off-topic on the kernel list anyway.

- David A. Holland | (please continue to send non-list mail to | yes, I moved.)

Any netkit mail should be sent to, not me.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:44    [W:0.037 / U:0.784 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site