From: Conn Clark <clark@esteem.com>
To: okorpil@fh-landshut.de
Cc: "Mészáros Lajos" <ludwigm@siemens.com>,
"Mark Chambers" <markc@mail.com>,
"Wells, Charles" <Charles.Wells@NielsenMedia.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Linux is not reliable enough?
Date: Tue, 27 Jul 2004 16:08:38 -0700 [thread overview]
Message-ID: <4106E076.60500@esteem.com> (raw)
In-Reply-To: <41068C9A.1000806@fh-landshut.de>
Oliver Korpilla wrote:
>
> Mészáros Lajos wrote:
>
>>
>> Yes, 'C' is unreliable because writing beyond the "maxindex" lets
>> you overwrite other's data, other's code and DOES make backdoor for
>> viruses.
>>
>> On the other hand testing every index every time for min and max slowes
>> the executing.
>
>
> QNX does not, and Linux does not, and with both C is as unreliable as ever.
>
> However, a failure in a QNX in the driver level is not as potentially
> malicious as in Linux. While this does not exclude failure, and does not
> say a thing about the actual quality of QNX or Linux code, it's a nice
> _additional_ feature related towards stability.
>
> I guess Linux lacking proper certification for some applications is a
> much bigger obstacle in the minds of managers, anyway.
>
> But somehow this is getting offtopic, quickly, isn't it?
>
> With kind regards,
> Oliver Korpilla
>
If C is not reliable enough then nothing is. In assembly(or even
handcoded machine language for the real hard core people) you can do
just about anything. Since all languages must resort to this at some
point, our foundation is built on sand and we are eternaly screwed.
Only the 4 last words of the last sentence of this statement is false.
Its not the languages job to write good solid code or verify it, its the
programmers responsibility. The only code you can truly trust is code
you have total control over. For truly solid code, no funky error
checking computer science language will ever replace good practices,
thorough testing, and documentation.
The reason for this is obvious, at some point higher level languages
must be built using a lower language to avoid the chicken/egg paradox.
Hence the quality of a higher level language can never be assured since
its foundation is made of sand.
Its a poor musician that blames their instrument.
-- Conn Clark
*****************************************************************
Give a man a match and you heat him for a moment. Set him on fire
and you'll heat him for life.
*****************************************************************
Conn Clark
Engineering Stooge clark@esteem.com
Electronic Systems Technology Inc. www.esteem.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-07-27 23:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-27 15:59 Linux is not reliable enough? Mészáros Lajos
2004-07-27 17:10 ` Oliver Korpilla
2004-07-27 23:08 ` Conn Clark [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-27 14:41 Wells, Charles
2004-07-27 15:20 ` Mark Chambers
2004-07-23 17:22 random ramblings on 8xx patches (long and tedious :-) 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
2004-07-26 7:49 ` 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
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=4106E076.60500@esteem.com \
--to=clark@esteem.com \
--cc=Charles.Wells@NielsenMedia.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=ludwigm@siemens.com \
--cc=markc@mail.com \
--cc=okorpil@fh-landshut.de \
/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).