From: "Kevin P. Dankwardt" <k@kcomputing.com>
To: "Embedded Linux PPC list" <linuxppc-embedded@lists.linuxppc.org>
Subject: Linux is not reliable enough?
Date: Fri, 23 Jul 2004 16:06:58 -0500 [thread overview]
Message-ID: <KCEOLLHGFJIAFNAMGACHMEMODPAA.k@kcomputing.com> (raw)
In-Reply-To: <20040723172210.5B396C109F@atlas.denx.de>
I am working with a team on a project where their customer is concerned
about the reliability of Linux. The customer wants to go with QNX because of
the belief that QNX Neutrino is inherently more reliable. This belief
revolves around the differences in design where drivers in QNX do not reside
in the same address space as the (micro-)kernel.
What the team was hoping to use is a MPC5200 based system and the ELDK.
The team needs to specifically address their customer's concern that a
single driver can crash the operating system in Linux, since the driver
resides in the same memory space as the kernel. They need to present
convincing arguments to the customer's Chief Software Architect.
Does anyone know of any good resources/references to address these concerns?
Any evidence, either way, that QNX Neutrino is more reliable?
Will the ELDK be adopting any of the Carrier Grade Linux requirements for
reliability? Any other projects like this of note?
Does anyone know of any embedded Linux projects where human lives really do
depend upon Linux to be robust and reliable?
Is UserMode Linux a possibility? Can one create custom drivers for UML and
mitigate risks that way?
Any clever ideas? Any clever, actually tested, ideas?
Despite all of the hype, would any of you be willing to look a customer in
the eye and say that an embedded Linux system can be reliable enough for
human lives to depend on it?
Thanks,
Kevin Dankwardt
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-07-23 21:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 12:00 random ramblings on 8xx patches (long and tedious :-) Robert P. J. Day
2004-07-22 17:46 ` Matt Porter
2004-07-23 12:34 ` Robert P. J. Day
2004-07-23 13:36 ` Wolfgang Denk
2004-07-23 14:09 ` Robert P. J. Day
2004-07-23 14:56 ` Wolfgang Denk
[not found] ` <410123EE.4000602@intracom.gr>
2004-07-23 15:56 ` Mark Chambers
2004-07-23 17:22 ` Wolfgang Denk
2004-07-23 21:06 ` Kevin P. Dankwardt [this message]
2004-07-24 3:02 ` Linux is not reliable enough? Linh Dang
2004-07-24 6:29 ` Der Herr Hofrat
2004-07-25 16:23 ` Wolfgang Denk
2004-07-24 11:35 ` Mark Chambers
2004-07-24 22:14 ` MPC8245 Error No. 26 DeLaGarza, Robert
2004-07-26 7:49 ` Linux is not reliable enough? Marius Groeger
2004-07-26 13:46 ` Mark Chambers
2004-07-26 14:31 ` Der Herr Hofrat
2004-07-26 15:42 ` Marius Groeger
2004-07-27 11:20 ` Robert Kaiser
2004-07-27 13:29 ` Mark Chambers
2004-07-24 21:44 ` Sylvain Munaut
2004-07-25 3:00 ` Could 2_4_devel support RPXlite DW LCD panel? Song Sam
-- strict thread matches above, loose matches on Subject: below --
2004-07-27 14:41 Linux is not reliable enough? Wells, Charles
2004-07-27 15:20 ` Mark Chambers
2004-07-27 15:59 Mészáros Lajos
2004-07-27 17:10 ` Oliver Korpilla
2004-07-27 23:08 ` Conn Clark
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=KCEOLLHGFJIAFNAMGACHMEMODPAA.k@kcomputing.com \
--to=k@kcomputing.com \
--cc=linuxppc-embedded@lists.linuxppc.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).