From owner-freebsd-current Tue Feb 6 05:02:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA19896 for current-outgoing; Tue, 6 Feb 1996 05:02:31 -0800 (PST) Received: from eel.dataplex.net (EEL.DATAPLEX.NET [199.183.109.245]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA19891 Tue, 6 Feb 1996 05:02:28 -0800 (PST) Received: from [199.183.109.242] (cod [199.183.109.242]) by eel.dataplex.net (8.6.11/8.6.9) with SMTP id HAA09503; Tue, 6 Feb 1996 07:02:12 -0600 X-Sender: rkw@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 6 Feb 1996 07:02:12 -0600 To: "Jordan K. Hubbard" From: Richard Wackerbarth Subject: Re: sup%d is broken - I agree Cc: hackers@freebsd.org, current@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk >> I must also report similar problems: >> [details of sup2..supn dysfunction elided] >Any suggestions on promoting and facilitating this level of >reliability? Would an `admin' mailing list for all FreeBSD.ORG >related resources help, or would it merely turn into a source of >unwanted messages for admins who already get too much mail? It >certainly doesn't seem like such reports should be sent to hackers, >anyway. There's too much traffic there. I concur. If we can direct the issues of distribution and coordination to a subset, it would help cut down on the traffic for those who have nothing to do with it. OTOH, there is some value in having the existance of a problem more generally known. All in all, I vote for a specialized list. If we set it up, then everyone needs to help in directing each discussion thread to the appropriate focused group. ---- Richard Wackerbarth rkw@dataplex.net