Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!godot!ima!inmet!tower
From: tower@inmet.UUCP
Newsgroups: net.news.group
Subject: Re: Orphaned Response
Message-ID: <1831@inmet.UUCP>
Date: Sun, 25-Nov-84 00:49:00 EST
Article-I.D.: inmet.1831
Posted: Sun Nov 25 00:49:00 1984
Date-Received: Mon, 26-Nov-84 01:57:28 EST
Lines: 32
Nf-ID: #R:amdahl:-51300:inmet:7000073:000:1242
Nf-From: inmet!tower    Nov 23 19:02:00 1984

Subject: better net.unix.* name and use

Re: net.news.group / amdahl!gam / 12:46 am  Nov 17, 1984
>    ...
>    net.unix.shells   - discussion of csh/sh/ksh, other shells, new shells
>    net.unix.kernel   - discussion of the kernel calls in section 2
>    net.unix.clib     - discussion of C library routines of section 3
>    net.unix-wizards.kernel - kernel esoterica
>    net.unix-wizards.drivers - device drivers problems/operations
>    
>    net.unix would be left for discussions of unix tools (grep, awk, etc).
>    ...
>    Gordon A. Moffett		...!{ihnp4,hplabs,amd,nsc}!amdahl!gam

1) I dislike two sub-groups ending in *.kernel.
How about
    net.unix.syscalls instead of net.unix.kernels ?
This name also better reflects the user's perspective.

2) I suspect that net.unix will be used for wider discussion of Unix
than non-command_processor tools, including discussion of the different
versions of Unix, and the O/S's history.

I also expect that net.unix-wizards will continue to see use
on topics like accounting, security, and administration.

-len tower		UUCP:     {ihnp4,harpo}!inmet!tower
 Intermetrics, Inc.	INTERNET: ima!inmet!tower@CCA-UNIX.ARPA
 733 Concord Ave.
 Cambridge, MA  02138	(617) 661-1840
 U.S.A.
----------