From: "Mark Chambers" <markc@mail.com>
To: "Kevin P. Dankwardt" <k@kcomputing.com>,
"Embedded Linux PPC list" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Linux is not reliable enough?
Date: Sat, 24 Jul 2004 07:35:36 -0400 [thread overview]
Message-ID: <000f01c47172$591008d0$0301a8c0@chuck2> (raw)
In-Reply-To: KCEOLLHGFJIAFNAMGACHMEMODPAA.k@kcomputing.com
Kevin,
I suspect you have a political problem here. Mr. Chief Software Architect
(which is a title for someone who doesn't actually *do* anything) is not
going to lose his job for choosing QNX. My suggestion is this: Point out
that the only way to prove reliability is with testing. Linux is open
source, it won't cost anything to put it on a side by side test, and let
Linux speak for itself.
- Linux is open source, any potential bugs are theoretically fixable. What
do you do if QNX develops a problem?
- You can hunt around for some of Linus's comments about microkernal
architecture. He thinks they're stupid, only he's says it more poetically.
- Don't fall into this trap of software mysticism, that one operating system
is somehow intrinsically more reliable than another. There's good and bad
software, to be sure, but even Windows can be reliable in certain carefully
constrained environments. It's only ones and zeros.
My $.02
Mark Chambers
----- Original Message -----
From: "Kevin P. Dankwardt" <k@kcomputing.com>
To: "Embedded Linux PPC list" <linuxppc-embedded@lists.linuxppc.org>
Sent: Friday, July 23, 2004 5:06 PM
Subject: Linux is not reliable enough?
>
> 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.
>
<snip>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-07-24 11:35 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 ` Linux is not reliable enough? Kevin P. Dankwardt
2004-07-24 3:02 ` Linh Dang
2004-07-24 6:29 ` Der Herr Hofrat
2004-07-25 16:23 ` Wolfgang Denk
2004-07-24 11:35 ` Mark Chambers [this message]
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='000f01c47172$591008d0$0301a8c0@chuck2' \
--to=markc@mail.com \
--cc=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).