From owner-freebsd-hackers Thu Apr 6 19:57:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lince.tdnet.com.br (lince.tdnet.com.br [200.236.148.6]) by hub.freebsd.org (Postfix) with ESMTP id D87DE37B5C4 for ; Thu, 6 Apr 2000 19:57:04 -0700 (PDT) (envelope-from kernel@tdnet.com.br) Received: from tdnet.com.br [200.236.148.100] by lince.tdnet.com.br with ESMTP (SMTPD32-5.00) id A21AEA9101DE; Thu, 06 Apr 2000 23:04:10 -0300 Message-ID: <38ED233E.74716D02@tdnet.com.br> Date: Thu, 06 Apr 2000 23:52:30 +0000 From: Gustavo V G C Rios X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Is traditional unixes kernel really stable ? References: <38ED128C.22C3AA28@tdnet.com.br> <20000406192206.N22104@fw.wintelcom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > > * Gustavo V G C Rios [000406 19:12] wrote: > > Considering the current kernel design approach used by traditional > > system, what happens if a drive were wrongly coded ? > > > > Would the entiry system crash ? > > please define "wrongly coded". Definition: the driver tries to access a memory outside its memory space. Worse yet: What about hardware buggy devices? This could case the entiry system to crash, isn't it ? -- If you're happy, you're successful. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message