Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP
id AA873 ; Mon, 08 Feb 93 19:00:26 EST
Path: sserve!manuel.anu.edu.au!munnari.oz.au!hp9000.csc.cuhk.hk!saimiri.primate.wisc.edu!sdd.hp.com!usc!howland.reston.ans.net!usenet.ins.cwru.edu!agate!agate.berkeley.edu!cgd
From: cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou)
Newsgroups: comp.unix.bsd
Subject: Re: Cost of 386bsd
Date: 7 Feb 93 15:56:06
Organization: Kernel Hackers 'r' Us
Lines: 32
Message-ID: <CGD.93Feb7155606@eden.CS.Berkeley.EDU>
References: <1kvc9dINNm2o@usenet.INS.CWRU.Edu> <1993Feb6.054843.22278@serval.net.wsu.edu>
<1993Feb6.084648.19785@wlbr.iipo.gtegsc.com>
<1993Feb6.175338.4973@netcom.com>
NNTP-Posting-Host: eden.cs.berkeley.edu
In-reply-to: hasty@netcom.com's message of Sat, 6 Feb 1993 17:53:38 GMT
In article <1993Feb6.175338.4973@netcom.com> hasty@netcom.com (Amancio Hasty Jr) writes:
>Along with the FREE price come ports and patches faster than any
>Corporation can crank out.
and to throw in my favorite two cents:
well, since 386bsd and BSD/386 are mostly source-compatible there's
going to be lots of cross-pollination...
for instance, my mh-6.7.whatever port was based on the port of LBL-MH 6.5 to
BSD/386...
386bsd and BSD/386 are aimed at different markets;
as much as i hate to say it, 386bsd is *definitely* not
capable of existing in a production environment,
if only because there's absolutely *NO* rational support.
while the net seems a great support service, if a company is
using a product to develop with, or whatever, and they find
a bug in that product, "oh, well, it looks like it could be the
'foo' problem, but you'll have to find it on your own" just
doesn't cut it...
chris
--
Chris G. Demetriou cgd@cs.berkeley.edu
"Sometimes it is better to have twenty million instructions by
Friday than twenty million instructions per second." -- Wes Clark