From owner-freebsd-questions@FreeBSD.ORG Tue Feb 15 05:49:25 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DD9716A4CE for ; Tue, 15 Feb 2005 05:49:25 +0000 (GMT) Received: from smtp11.wanadoo.fr (smtp11.wanadoo.fr [193.252.22.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB97743D3F for ; Tue, 15 Feb 2005 05:49:24 +0000 (GMT) (envelope-from atkielski.anthony@wanadoo.fr) Received: from me-wanadoo.net (unknown [127.0.0.1]) by mwinf1106.wanadoo.fr (SMTP Server) with ESMTP id 2C29B1C00090 for ; Tue, 15 Feb 2005 06:49:24 +0100 (CET) Received: from pix.atkielski.com (ASt-Lambert-111-2-1-3.w81-50.abo.wanadoo.fr [81.50.80.3]) by mwinf1106.wanadoo.fr (SMTP Server) with ESMTP id 051A61C00087 for ; Tue, 15 Feb 2005 06:49:23 +0100 (CET) X-ME-UUID: 20050215054924209.051A61C00087@mwinf1106.wanadoo.fr Date: Tue, 15 Feb 2005 06:49:23 +0100 From: Anthony Atkielski X-Priority: 3 (Normal) Message-ID: <501532379.20050215064923@wanadoo.fr> To: freebsd-questions@freebsd.org In-Reply-To: References: <200502112313.28082.hindrich@worldchat.com> <823196404.20050212105644@wanadoo.fr> <420DE422.3020102@wanadoo.es> <1546398643.20050212123202@wanadoo.fr> <420E0164.7090300@wanadoo.es> <1587470376.20050215001857@wanadoo.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: Freebsd vs. linux X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Feb 2005 05:49:25 -0000 Eric Kjeldergaard writes: > Well, that's simply not true. Windows (At least XP, can't remember if > this happens on 2k or not) definitely states that the error that > caused the crash is or is not a driver. It says something to the > effect of "The system crash was caused by a bad driver." I suppose it may isolate messages better than its predecessors. > You read the code, I'm sure you know where that message gets > generated. These operating systems contain millions of lines of code. I haven't read them all. Nobody has. > As windows is largely infallible, I'm sure they have some way of > keeping straight which portion of the kernelspace is drivers and which > isn't. You overestimate the capabilities of the OS. In many cases it is possible to roughly or precisely localize a fault in kernel space, but at other times it is not. Bugs in one area of an OS (defined as anything with kernel privileges) can cause faults in other areas. > Yeah, they kinda are. If they are on the operating system cd, they > are part of the operating system. There are lots of things on CDs that are not part of the OS. > An operating system is just a software package. In this context, one can think of the operating system as the aggregate of permanent code executing with kernel privileges. Drivers execute with these privileges but they are essentially add-ons. They aren't written by the same people and they usually aren't written and tested with the same rigor. -- Anthony