Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!uniwa!cujo!marsh!cproto From: cproto@marsh.cs.curtin.edu.au (Computer Protocol) Subject: Re: 386bsd -- The New Newsgroup Message-ID: <cproto.716042678@marsh> Keywords: newsgroup 386bsd news group Sender: news@cujo.curtin.edu.au (News Manager) Organization: Curtin University of Technology References: <1992Sep8.140141.10371@terminator.cc.umich.edu> <18iprpINNg6e@agate.berkeley.edu> <1992Sep8.200625.2894@socrates.umd.edu> <veit.716026274@du9ds3> Date: Wed, 9 Sep 1992 12:44:38 GMT Lines: 60 veit@du9ds3.uni-duisburg.de (Holger Veit) writes: >In <1992Sep8.200625.2894@socrates.umd.edu> john@socrates.umd.edu (John VanAntwerp) writes: >>In article <18iprpINNg6e@agate.berkeley.edu> wjolitz@soda.berkeley.edu (William F. Jolitz) writes: >>> >>>As per Bill's suggestion, here's a breakdown of some of the suggested >>>topics and groups: >>> >>> comp.os.386bsd (general questions and trivia) >>> comp.os.386bsd.kernel (discussion on kernel content/structure) >>> comp.os.386bsd.windows (ditto, on windowing systems like X) >>> comp.os.386bsd.sharedlib (shared library and programming environment) >>> comp.os.386bsd.net (networking topics) >>> comp.os.386bsd.bugs (new bugs) >>> comp.os.386bsd.ann (announcements, fixes, additions) >>I think that this is a fine set of newsgroups... >> John >You should not multiply entities unless it is absolutely necessary >(free translation of William of Occam's well-known statement). >We have considerably high traffic on 'I cannot boot with my configuration', say >'newbie' stuff. Since I follow this group quite long, I would have an idea >where to post such a question, but if I were a beginner and desperate >because of 386bsd had just cleaned my whole disk, I would perhaps ignore >the different groups and send my mail to all of them, perhaps to find >one who can answer. >I haven't seen much on shared libraries yet in this group, so why sharedlib. >Or did I misunderstand this, because you mean a common library (archive) for >all who want to share software? This might be called 'comp.os.386bsd.contrib'. >I if found just a bug in /sys/kern/kern_execve.c, should I post to >comp.os.386bsd.bugs or c.o.3.kernel, just because my detected effects could be >for interest for the latter group as well? And if I fixed the bug on the fly, >should I also send it to c.o.3.ann? Similiar things might happen with >network related things. >BTW, when the AT&T/USL or similiar junk should come up again, where will it >go? I assume from the previous stories (before alt.suit-bsdi ?) was created, >the articles were scattered around everything that had *.unix.* in its name. >*** I am not against a new group comp.os.386bsd, but why should it be a whole >*** tree directly? Confusion will be built-in. I couldn't agree more. I don't even see the need to change the current status quo. All traffic in this newsgroup is related to 386bsd (forget the 0.001% exceptions). Its seems completely crazy to disturb something which works well (don't fix something which ain't broken). So please leave things as they are - but at least please please please don't create 20 different newsgroups all with duplicate messages (people will crosspost). There are plenty of us who dial in from home with 1200 or 2400 b/s and read mail and news. So it's a real pain having to sift through the some message several times. Regards - Tibor Sashegyi (cproto@abel.cs.curtin.edu.au)