From owner-freebsd-hackers Fri Apr 7 8:23:20 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 B5BFD37B99F for ; Fri, 7 Apr 2000 08:23:11 -0700 (PDT) (envelope-from kernel@tdnet.com.br) Received: from tdnet.com.br [200.236.148.134] by lince.tdnet.com.br with ESMTP (SMTPD32-5.00) id A0E2646001B8; Fri, 07 Apr 2000 11:29:54 -0300 Message-ID: <38EDD209.421EF9B0@tdnet.com.br> Date: Fri, 07 Apr 2000 12:18:17 +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> <38ED233E.74716D02@tdnet.com.br> <20000406230234.B4381@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: > > Some archs (such as i386) allow the OS to set page protections and > io permission bitmaps that effectively can pretect against problems > with drivers touching incorrect IO ranges, however... > > > > > Worse yet: What about hardware buggy devices? > > This could case the entiry system to crash, isn't it ? > > Yes, incorrectly programmed hardware either by firmware (on > chip/board) or by drivers can cause crashes and hardware damage. > That's the point! Why not a different approach ? Why not starting a microkernel arch? The microkernel would basically do just feel tasks, like: IPC: managing and routing messages. Process scheduling. First level interrupt handling. All other tasks would run in like any other user process, like a fyle system daemon, process daemon , internet daemon (not inetd), and, of course, device drivers programs. This design, would not let a system crash due to device drivers problems or even bad hardware desgin. What all you think about that ? -- 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