Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!agate!howland.reston.ans.net!xlink.net!zib-berlin.de!news.tu-chemnitz.de!irz401!narcisa.sax.de!not-for-mail
From: j@narcisa.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Slight flame from Linux user
Date: 12 Jun 1995 11:35:25 +0200
Organization: Private U**x site, Dresden.
Lines: 28
Message-ID: <3rh1ot$lnj@bonnie.tcd-dresden.de>
References: <3ql3gd$je2@bell.maths.tcd.ie> <3qpfm0$76j@bell.maths.tcd.ie> <3r166m$fit@bonnie.tcd-dresden.de> <D9t6un.EqI@citylink.dinoex.sub.org>
Reply-To: joerg_wunsch@uriah.heep.sax.de
NNTP-Posting-Host: 192.109.108.139
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Moin Peter!
Peter Much <peter@citylink.dinoex.sub.org> wrote:
>>>> Fatal signal 11 syndrome is almost always a HARDWARE PROBLEM -
>That's _NO_ hardware-problem. The day before yesterday we installed
>a Linux 1.2.8 onto one of our hardware-gurus' portable. The platform has
>already run other OS', at least an older Linux, maybe some *BSDs too.
``Absence of evidence is no evidence of absence.''
Your simple observation that a particular problem happens only with a
particular software environment is not a proof for wrong software. (I
don't claim it were *not* Linux' fault here -- but you did by no way
prove that it actually *is*. You've only written your *observation*.)
>>I'm surprised about your conclusion. I hope you are aware that
>>FreeBSD is using just the same gcc you're blaming here?
>
>The linux kernel is loosing interrupts.
How the hell do losing interrupts correspond to Sig 11's?
--
cheers, J"org private: joerg_wunsch@uriah.heep.sax.de
http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)