From owner-freebsd-hackers Sat Feb 27 14:54:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id B36AB14BDA for ; Sat, 27 Feb 1999 14:54:47 -0800 (PST) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.8.8/8.6.9) with SMTP id RAA27543; Sat, 27 Feb 1999 17:56:15 -0500 (EST) Message-Id: <199902272256.RAA27543@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 27 Feb 1999 18:04:39 -0500 To: Chuck Robey From: Dennis Subject: Re: Cobalt blames linux for their security problems! Cc: hackers@freebsd.org In-Reply-To: References: <199902271927.OAA26965@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:56 PM 2/27/99 -0500, you wrote: >On Sat, 27 Feb 1999, Dennis wrote: > >> At 09:18 PM 2/27/99 +1030, you wrote: >> >On Saturday, 27 February 1999 at 2:16:02 -0500, mike@seidata.com wrote: >> >> On Fri, 26 Feb 1999, Julian Elischer wrote: >> >> >> >>> There's a good idea.. use a free OS and then blame it for your problems.. >> >> >> >> Tell me about it... here's my response. >> >> >> >> >> >> [snip] >> >> >> >> >> >> I had actually looked into some of Cobalt's products... must say I've >> >> lost quite a bit of respect for them as a result of their reponse to >> >> this issue. Then again, what's to consider anyway... They don't run >> >> FreeBSD. ;) >> > >> >They could just as well have run FreeBSD. The issue here is that they >> >(or somebody else) are blaming the OS for their own mistakes. >> >> Well the RAQ is a RISC processor that FreeBSD doesnt support, so I dont >> think that that was an option. Blaming an OS is an OK thing I think...you cant >> as a vendor be expected to fix everything thats wrong....PCI shared memory on >> secondary buses doesnt seem to work in FreeBSD2.2 (havent tried 3.1 yet)... >> you have to blame the OS as its not practical to fix it yourself. > >Dennis, did you read enough of that article? Their problem was leaving >around a .history file, it hadn't anything at all to do with pci >probing. > >That article had more factual screwups (on both sides, to be fair) than >I can believe ... let's not make it worse by skimming the facts to fit >our moods. I was generalizing more on the point that many seemed to be making that you shouldnt blame a free OS for its fallacies that the specifics of the cobalt situation. Sorry if I didnt make that clear. Dennis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message