home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.bsd
- Path: sparky!uunet!elroy.jpl.nasa.gov!usc!wupost!csus.edu!netcom.com!netcomsv!resonex!michael
- From: michael@resonex.com (Michael Bryan)
- Subject: Re: 386bsd -- The New Newsgroup
- Message-ID: <1992Sep8.154156.2672@resonex.com>
- Keywords: newsgroup 386bsd news group
- Organization: Resonex Inc., Sunnyvale CA
- References: <1992Sep8.140141.10371@terminator.cc.umich.edu> <18iprpINNg6e@agate.berkeley.edu>
- Date: Tue, 8 Sep 1992 15:41:56 GMT
- Lines: 34
-
- In article <18iprpINNg6e@agate.berkeley.edu> wjolitz@soda.berkeley.edu (Lynne 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 hardly think we need such an extensive list of groups at this time.
- Just a single group "comp.os.386bsd" should suffice for starters.
- After time, a split could be voted on if traffic increases.
-
- If we *really* must create multiple groups, I'd suggest the following
- alternate plan:
-
- comp.os.386bsd.announce [Moderated?]
- comp.os.386bsd.bugs
- comp.os.386bsd.misc
-
- Notice there should be no separate upper-level group if we start
- with a split (use .misc instead), and ".ann" should be ".announce"
- to be more like other groups.
-
- I really think a single new newsgroup is currently adequate, however.
-
- --
- Michael Bryan michael@resonex.com "Milk and Cheese in '92!" | ,_,
- "Lovers are like... dentures. You don't want them in your | /oo \
- mouth all night, but you sure as hell want them within arm's | <>__|
- reach in the morning!" --- Miss Elmira Gulch | | U|
-