Chris,
you are right, in my translation I did not mention real time
linux explicitely but all statements refer to it. This causes
misunderstanding.
1. There is no standard available being appropriate for
characterizing hard real time
> The correct translation is "Linux does not provide by default behaviour
> suitable for real-time". This is a valid criticism of Linux.
Applied to Linux you are right, implicitely I applied it to
real time linux. Here it seems to be true, too ?
> 3. There is no standard API available
> The correct translation is "There is no standard real-time API".
Yes, this is better. But since the article was on real time linux,
I did not mention it expressis verbis.
In general I thought the first email with the disadvantages as
input for real time linux development. An implicitely I set
real time linux to RTL or RTAI. Of course Lynx RTS is completely
different. Sorry, Mea culpa mea maxissima culpa, et culpa rubet
vultus meus.
peterw
--
Dr. Peter Wurmsdobler
CTM - Centre de Transfert des Microtechniques
39, av. de l'Observatoire, BP-1445, 25007 Besancon CEDEX 3
TELEPHONE: +33 3 81 47 70 20 TELECOPIE: +33 3 81 47 70 21
E-mail: [EMAIL PROTECTED]
Ceterum censeo MIRCOSOFTem esse delendam.
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
---
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
