From owner-freebsd-current  Mon Feb  5 23:01:30 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id XAA03811
          for current-outgoing; Mon, 5 Feb 1996 23:01:30 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [192.216.222.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA03806
          Mon, 5 Feb 1996 23:01:28 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id XAA01709; Mon, 5 Feb 1996 23:01:18 -0800
To: uhclem@nemesis.lonestar.org (Frank Durda IV)
cc: hackers@freebsd.org, current@freebsd.org
Subject: Re: sup%d is broken - I agree 
In-reply-to: Your message of "Mon, 05 Feb 1996 22:36:00 +0700."
             <m0tjf8T-000COKC@nemesis.lonestar.org> 
Date: Mon, 05 Feb 1996 23:01:17 -0800
Message-ID: <1707.823590077@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
Precedence: bulk

> I must also report similar problems:
> [details of sup2..supn dysfunction elided]

Well, I'm glad you're reporting them, that's all I can really say.
Truly!  I think that central resources should be flagged ASAP when
broken and people should take Extra Special Care in making sure they
run right, just as we jump up and down and run around in paniced
circles whenever freefall starts having problems.  We might not fix
things right away, but we certainly manage to look busy! :-)

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.

					Jordan