Return to BSD News archive
Newsgroups: comp.unix.bsd
Path: sserve!manuel!munnari.oz.au!uunet!emba-news.uvm.edu!trantor.emba.uvm.edu!wollman
From: wollman@trantor.emba.uvm.edu (Garrett Wollman)
Subject: Re: Announcing 386BSD Release 0.1
Message-ID: <1992Jul20.135540.12384@uvm.edu>
Sender: news@uvm.edu
Organization: University of Vermont, EMBA Computer Facility
References: <14cuvtINN568@agate.berkeley.edu>
Date: Mon, 20 Jul 1992 13:55:40 GMT
Lines: 32
In article <14cuvtINN568@agate.berkeley.edu> wjolitz@soda.berkeley.edu (William F. Jolitz) writes:
>by asking your news coordinator to subscribe to it. We do
>not recommend using comp.unix.bsd, since 386BSD, like linux
>and mach, is not a "comp.unix" system.
Sorry, but this argument is bogus. A few points:
1. comp.unix.bsd was created to handle the overflow from
comp.unix.sysv386 after BSDI (yes, big, bad BSDI) announced their
product.
2. AIX sure as hell isn't ``comp.unix'' either, but the newsgroup
is called `comp.unix.aix'.
3. As far as everybody who is not employed by AT&T and its
licensees is concerned, BSD *is* UNIX, whether it actually contains
AT&T code or not.
Now, if you wanted to claim that the 386BSD-related traffic in
comp.unix.bsd is drowning out all the people who are interested in
other forms of BSD, I would have sympathy for that argument. It would
then make sense to create `comp.unix.bsd.jolix'. The last thing we
need is more confusion between 386BSD and BSD/386.
-GAWollman
--
Garrett A. Wollman = wollman@emba.uvm.edu = UVM is welcome to my opinions
= uvm-gen!wollman =
That's what being alive is all about. No deity, no higher goal
exists, than to bring joy to another person. - Elf Sternberg