Date: Tue, 15 Feb 2005 01:43:37 +0100 From: Anthony Atkielski <atkielski.anthony@wanadoo.fr> To: freebsd-questions@freebsd.org Subject: Re: Freebsd vs. linux Message-ID: <16113082.20050215014337@wanadoo.fr> In-Reply-To: <d9175cad0502141557114178e7@mail.gmail.com> References: <200502112313.28082.hindrich@worldchat.com> <823196404.20050212105644@wanadoo.fr> <420DE422.3020102@wanadoo.es> <1546398643.20050212123202@wanadoo.fr> <420E0164.7090300@wanadoo.es> <d9175cad0502140942a7244b2@mail.gmail.com> <1587470376.20050215001857@wanadoo.fr> <d9175cad0502141557114178e7@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Eric Kjeldergaard writes: > Well, no that's not entirely true...First off, there's the claim by > Windows itself that it's not drivers. The OS itself never identifies problems as being within the drivers. Driver code is assimilated with the kernel while it is running. > You've read the code (as you say) and know that Windows wouldn't > possibly lie about the fact that it's not the drivers. Sure it would. Most error messages are generic; few programmers are conscientious enough to put in extremely detailed and specific error messages. And in some cases the OS doesn't really know what happened, especially for faults in the kernel (or the drivers, which are assimilated with the kernel, as I've said). > And then there's the thing where since one is including drivers along > with an operating system, they are part of the operating system even > if they were written by a third party. They are not part of the operating system. -- Anthony
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16113082.20050215014337>