From owner-freebsd-current Mon Nov 16 20:50:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA13403 for freebsd-current-outgoing; Mon, 16 Nov 1998 20:50:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (tex-30.camalott.com [208.229.74.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA13398 for ; Mon, 16 Nov 1998 20:50:10 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id WAA01425; Mon, 16 Nov 1998 22:49:38 -0600 (CST) (envelope-from joelh) To: Open Systems Networking Cc: Bryan Fullerton , freebsd-current@FreeBSD.ORG Subject: Re: proc changes References: From: Joel Ray Holveck Date: 16 Nov 1998 22:49:37 -0600 In-Reply-To: Open Systems Networking's message of "Sun, 15 Nov 1998 16:02:28 -0500 (EST)" Message-ID: <86pvamzzxa.fsf@detlev.UUCP> Lines: 21 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > *grumble* *grumble* > Ok for the Nth time :-) > You need to rebuild libkvm and associated utils and build a new kernel. > Im wondering if anyone reads current. :) > Actually ive been guilty of that myself in the past you dont read the > HEADS-UP or the repeated threads till your bitten. then its too late cause > they threads have died. Oh well maybe one day well get that real-time > trouble ticket system on the web :-) Okay, what do you think of having lists with *only* heads-up info for -current and -stable, with easily accessible archives? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message