From owner-freebsd-current Sun Sep 17 17:33:12 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA08385 for current-outgoing; Sun, 17 Sep 1995 17:33:12 -0700 Received: from wiley.csusb.edu (wiley.csusb.edu [139.182.2.2]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id RAA08380 for ; Sun, 17 Sep 1995 17:33:10 -0700 Received: by wiley.csusb.edu (5.67a/1.34) id AA21675; Sun, 17 Sep 1995 17:38:12 -0700 From: rmallory@wiley.csusb.edu (Rob Mallory) Message-Id: <199509180038.AA21675@wiley.csusb.edu> Subject: Current status report To: freebsd-current@freebsd.org Date: Sun, 17 Sep 1995 17:38:12 -0700 (PDT) X-Mailer: ELM [version 2.4 PL22] Content-Type: text Content-Length: 1190 Sender: owner-current@freebsd.org Precedence: bulk I'm not one to rag on anyone directly; but it's amazing how quiet everyone has been with the current ~sys brokeness in -current. Everyone should be *proud* that there has not been an uproar (at least not on the public mailing lists) about the 3-week lack of a stable kernel. Don't even think about screaming "Current is for those who ..." I have been on -hackers since 1.0. I am lucky [wise] enough to have a spare 1gig drive with a 'current/stable' OS and src tree. ...there are many less fortunate -current users who are "afraid" to speak up (for fear of being flamed, killfile'd, or blacklisted) who are having to re-install 2.1SNAP or sup -stable. I just want to acknowlege those [we] -current users, and possibly get a satisfyingly-complete status report on the current state of the ~sys tree. I really want to get back to testing the new stuff in -current! like the ncr825, userconfig, vm-performance, gus, ... Its hard waiting alone in the dark. issues: (you all know the questions wanted answered) John: I know you're working hard, and we're waiting patiently. PHK: + Crack kills! :) Jordan: Can i have a free tee-shirt? -Rob Mallory [rmallory@csusb.edu]