> It is only the consequences that matter, and the OS can not determine
> how expensive the consequences are. Humans let the OS know, and the
> OS must avoid missing deadlines.
Humans must *make* the OS avoid missing deadlines, if they are designing
the OS or the system.
> (so it was bad to bother Richard Gooch with such a pointless question)
The original error I pointed out (whose, I don't remeber, but it was
consistent) was a completely different confusion: shortness of deadline
and/or very low slack time/permissible latency was being confused with
the hardness of the real time system. You may have pooh-poohed a
clarification of a different error, but nonetheless you seem to be
scoffing without understanding what you're scoffing at. If I knew of
a good RTOS book, I'd be recommending it to you right now.
Keith
-- "The avalanche has already started; |Linux: http://www.linuxhq.com |"Zooty, it is too late for the pebbles to |KDE: http://www.kde.org | zoot vote." Kosh, "Believers", Babylon 5 |Keith: kwrohrer@enteract.com | zoot!" www.midwinter.com/lurk/lurker.html |http://www.enteract.com/~kwrohrer | --Rebo- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/