*BSD News Article 26361


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!bunyip.cc.uq.oz.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!zip.eecs.umich.edu!umn.edu!gaia.ucs.orst.edu!news.uoregon.edu!usenet.coe.montana.edu!bsd.coe.montana.edu!nate
From: nate@bsd.coe.montana.edu (Nate Williams)
Newsgroups: comp.os.386bsd.questions
Subject: Re: <Proposal> Rename of the 386bsd groups
Date: 21 Jan 1994 21:39:00 GMT
Organization: Montana State University - Bozeman MT
Lines: 25
Message-ID: <2hpi1k$9vv@pdq.coe.montana.edu>
References: <ETLDNCN.94Jan21133424@paddington.ericsson.se>
NNTP-Posting-Host: bsd.coe.montana.edu

In article <ETLDNCN.94Jan21133424@paddington.ericsson.se>,
 <etldncn@paddington.ericsson.se> wrote:
>Hi BSD fans,
>
>I have a suggestion. Why not rename all the comp.os.386bsd groups to
>comp.unix.pc.net2bsd or comp.unix.net2bsd? 

Not to throw water at the idea, but do you have any idea how much work
it would be to do this.  Granted, there is a confusion factor, but IMHO
the content of the postings are still by far related to BSD on the Intel
x86 (X >= 3) architecture, so 386bsd is still a valid name even though
it WAS a specific version of BSD for the x86 machines.  (Very few people
still install it, and those that have it installed at least know about
the newer versions via this newsgroup and know where to post)

For non-intel BSD's, I think comp.unix.bsd is the place to go.


Nate

-- 
nate@bsd.coe.montana.edu     |  Freely available *nix clones benefit everyone,
nate@cs.montana.edu          |  so let's not compete with each other, let's
work #: (406) 994-4836       |  compete with folks who try to tie us down to
home #: (406) 586-0579       |  proprietary O.S.'s (Microsloth) - Me