Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!spool.mu.edu!uunet!mcsun!Germany.EU.net!unidui!du9ds3!veit From: veit@du9ds3.uni-duisburg.de (Holger Veit) Newsgroups: comp.unix.bsd Subject: Re: 386bsd -- The New Newsgroup Date: 9 Sep 92 08:11:14 GMT Organization: Uni-Duisburg FB9 Datenverarbeitung Lines: 52 Message-ID: <veit.716026274@du9ds3> References: <1992Sep8.140141.10371@terminator.cc.umich.edu> <18iprpINNg6e@agate.berkeley.edu> <1992Sep8.200625.2894@socrates.umd.edu> Reply-To: veit@du9ds3.uni-duisburg.de NNTP-Posting-Host: du9ds3.uni-duisburg.de Keywords: newsgroup 386bsd news group 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. Holger -- | | / Dr. Holger Veit | INTERNET: veit@du9ds3.uni-duisburg.de |__| / University of Duisburg | BITNET: veit%du9ds3.uni-duisburg.de@UNIDO | | / Dept. of Electr. Eng. | "No, my programs are not BUGGY, these are | |/ Inst. f. Dataprocessing | just unexpected FEATURES"