Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.kei.com!news.mathworks.com!newsfeed.internetmci.com!news.starlink.com!usenet From: alschnei@starlink.com (Alan Schneider) Newsgroups: comp.unix.bsd.bsdi.misc Subject: Re: BSDI Hardware support for... Date: Thu, 28 Sep 1995 19:08:44 GMT Organization: Star Link Internet Services Lines: 30 Message-ID: <44da61$me5@pegasus.starlink.com> References: <441rto$d93@hihat.mwci.net> NNTP-Posting-Host: pm1-22.starlink.com X-Newsreader: Forte Free Agent 1.0.82 Just browsing and saw your message... I learned early on that when it comes to hardware NOT on the BSDI support list, things get very bad... We tried installing 2.0 on an HP Server. Because it is so proprietary, a lot of the 'features' of that server were not available. Also, we had to ditch the on board SCSI in lieu of a BusLogic. We have also built 3 servers that were 'clones' which, when loaded with BSDI 2.0, ran fine the first time with no problems. It has been my experience that proprietary systems and BSDI don't always get along. Not to say that the COMPAQ won't, but I know Compaq is high on proprietary 'enhancements'. That's my 2cents. Help Desk <help@mwci.net> wrote: >Compaq Proliant 1000 Server > Compaq NetFlex-2 ENET-TR (CPQ6101) > Compaq Integrated 32-Bit Fast-SCSI-2 Controller >Will BSDI run on this and find this hardware? >Jeremie Miller >jmiller@mwci.net