From: bmcbrine@hakatac.almanac.bc.ca (Bill T. McBrine) Subject: Re: Splitting comp.os.linux, again Date: 20 Oct 1992 00:12:19 GMT
Hmmm, lets see what my ideas stir up....
In article <1992Oct17.074551.4974@klaava.Helsinki.FI> laakkone@klaava.Helsinki.FI (Tero Laakkonen) writes:
>In <MAGNUS.92Oct17015210@bark-fddi.ii.uib.no> magnus@bark-fddi.ii.uib.no (Magnus Alvestad) writes:
>
>>I agree. It is impossible to keep up with this volume without using
>>more time for it than it is worth. I say we split, then take the
>>problems as they come.
>
>hmm. i suggest that everybody learn to use their news readers or consider
>getting a proper news reader first. i think news reader faq's are
>archived somewhere in rtfm.mit.edu in /pub/usenet...
>
>if you notice that you're already using the best possible news reader and you
>just don't like reading tons of rubbish news, consider learning new
>commands like 'K', etc. that way you can decide what's rubbish and what
>ain't. read your news reader manual.
I have read the man pages for trn I'm using, and I know how to use it but I
do feel that c.o.linux _needs_ to be split. At least to cut down on the
amount of novice-type questions and problems that everyone has.
I for one am just unable to read this group Every Day, I just don't have the
time for it. And when I get to the linux conference I get somewhat disheartened
when I see the 500-800 messages to wade through. Now, I'm not complaining
of the throughput this group gets. Thats great this OS is getting so much
interest. However, we are talking about distributing Linux on either disks
or CD-Rom, so there will Always be LOTS of newbie type questions or problems.
The amount of posts by new users will increase, not decrease. For this reason
I think it's important to split the group at least once. I know bbsing/netting
is like a big family, but we won't be going anywhere just because we make
two or more groups instead of one?
This is my own idea on sub-linux conferences.
comp.os.linux -- stays for announcements, kernel updates etc...
comp.os.linux.newbie --- for new user type questions, or problems.
comp.os.linux.apps --- chat about application level bugs, fixes,
mods, whatever.
That's it. No radical changes, no restructuring, no pain. Right?
>stop using long signatures. you don't have to use a ".sig" because
>the guy next to you does.
>
>indicate in the subject line if you wanna know something or if you wanna
>tell someone something.
>
>stop whining.
>
>hope this helped.
>
>-tero
The subject line can only say so much for a message. And of course, there
will always be ambiguous or vague subject lines...
l8r... !{] Bill.
Me whine? Naah! 8-]