Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!metro!basser.cs.su.oz.au!news.adelaide.edu.au!gateway.dircsa.org.au!apanix!cleese.apana.org.au!cleese.apana.org.au!not-for-mail
From: newton@cleese.apana.org.au (Mark Newton)
Newsgroups: comp.os.386bsd.questions
Subject: Re: <Proposal> Rename of the 386bsd groups
Date: 26 Jan 1994 11:52:20 +1030
Organization: cleese.apana.org.au public access UNIX +61-8-3736006
Lines: 24
Distribution: world
Message-ID: <2i4gkq$i1r@cleese.apana.org.au>
References: <ETLDNCN.94Jan21133424@paddington.ericsson.se>
NNTP-Posting-Host: cleese.apana.org.au
In article <ETLDNCN.94Jan21133424@paddington.ericsson.se> etldncn@paddington.ericsson.se ( ) writes:
>I have a suggestion. Why not rename all the comp.os.386bsd groups to
>comp.unix.pc.net2bsd or comp.unix.net2bsd?
>
>I ask this because I think many people are confused by the fact the
>the group is called 386bsd but 386bsd 0.1 is effectively obsolete. Why
>not give a more generic name that will cover NetBSD, FreeBSD and any
>future release of 386BSD?
I have a suspicion that the kind of people who will be confused about the
"386bsd" nomenclature will be even more confused about the "net2"
naming scheme, because they won't have the faintest idea about what Net/2
actually is (remember, we're talking about very new users here -- anyone
who's been around for a while will have learned how to cope with the
current screwy names).
I think the groups really do belong in the comp.os heirarchy, too.
- mark
--
--------------------------------------------------------------------
I tried an internal modem, newton@cleese.apana.org.au
but it hurt when I walked. Mark Newton
----- Voice: +61-8-3735575 --------------- Data: +61-8-3736006 -----