🚀 go-pugleaf

In article <cwatters@magnus.acs.ohio-state.edu (Coyt D Watters) writes:
>>>> comp.sys.x86.video
>>>> comp.sys.x86.drive
>>>> comp.sys.x86.hardware   (motherboard, memory, mouse, sound, keyboards,etc)
>>>> 
>>>> and get rid of comp.sys.ibm.pc.*
>>>
>>>Great idea! How about one more division:    comp.sys.x86.software
>>
>>Definitely a good idea! Could we add: comp.sys.x86.audio
>
>Since the P5 is officially the PENTIUM, and there are systems using V20, V30
>and 8088 processors out there, I think the .x86. designator may not be the 
>best for naming.  Maybe the generic "pc" could be used, though all the 
>competing architectures (Amiga, Mac, etc) can claim that they are also
>"personal computers".

Well, the V20 and V30 are just 8088's and 8086's that emulate 80286's, and
it's an established fact that the Pentium is a marketing gimmick and the
market place would probably be more willing to use the term 586 anyways
(ie Intel created a standard family nomenclature, so let's hold them to it).

>comp.sys.pc.hardware.misc
>comp.sys.pc.hardware.drives
>comp.sys.pc.hardware.video
>comp.sys.pc.hardware.audio
>comp.sys.pc.software.misc

I think that the .software part is unnecessary as there are other groups
that deal with specific applications.  IMHO the comp.sys.x86 or comp.sys.pc
hierarchy should deal with hardware topics and software drivers for hardware
components.

So I would think that leaves us with either comp.sys.x86.* or comp.sys.pc.*,

I think there should be a .help group so that people that join the group to
ask a fast (and usually trivial) question without reading previous posts or
FAQ's can post in that group (and reduce the noise in other groups).

Don't you hate the post with the subject line -> HELP!!!!! or MY COMPUTER
DIED WHAT SHOULD I DO!!!???

I think the most thought should be put into creating a set of groups that
focus on the combinations of what most people find interesting, ie
if sound cards and video go together for most people, then there would be
no sense to split them into different groups.  I would also avoid the
.misc name because it is too vague, and cross-posting would be high (as it
is now with .misc and .hardware).