Xref: utzoo comp.sys.amiga:45725 news.groups:15657
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!ames!think!zaphod.mps.ohio-state.edu!rpi!brutus.cs.uiuc.edu!apple!oliveb!amiga!cbmvax!amix!ag
From: ag@amix.commodore.com (Keith Gabryelski)
Newsgroups: comp.sys.amiga,news.groups
Subject: Re: Splitting Up Comp.Sys.Amiga
Message-ID: <207@amix.commodore.com>
Date: 14 Dec 89 23:40:36 GMT
References: <6073@nigel.udel.EDU>
Reply-To: ag@amix.commodore.com (Keith Gabryelski)
Followup-To: news.groups
Organization: Commodore Amix Development
Lines: 30

This is mostly to set followups to news.groups so this discussion
won't float in comp.sys.amiga forever but I do have something to
contribute.

In article <6073@nigel.udel.EDU> peterson@fsucs.cs.fsu.edu
(Eric J. Peterson) writes:
>   comp.sys.amiga.tech -- Same as the current group, which is for highly
>      technical postings regarding hardware and AmigaDOS (and Amix as
>      well hopefully! 8-)

Personally, I think Amix should be set aside from AmigaDos (which
should be comp.os.amiga by all rights).  comp.unix.amix makes sense to
me.

Currently there are a lot of messages in comp.sys.amiga.  I have a
kill file that only keeps those messages with the words AMIX or UNIX
in them to save time myself a lot of grief.

I see:

	comp.sys.amiga				# The system noise group
	comp.sys.amiga.tech			# Hacking the system
	comp.os.amiga OR comp.os.amigados	# AmigaDos questions
	comp.unix.amix				# Amix questions

and remove crossposting rights between these three groups :-).

Pax, Keith
-- 
ag@amix.commodore.com        Keith Gabryelski          ...!cbmvax!amix!ag