From owner-freebsd-current Sat Sep 19 18:32:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05006 for freebsd-current-outgoing; Sat, 19 Sep 1998 18:32:43 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA04988 for ; Sat, 19 Sep 1998 18:32:32 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id SAA15343; Sat, 19 Sep 1998 18:32:38 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: dan@math.berkeley.edu (Dan Strick) cc: smp@csn.net, freebsd-current@FreeBSD.ORG Subject: Re: A new SNAPshot is finally on current.freebsd.org In-reply-to: Your message of "Sat, 19 Sep 1998 17:47:53 PDT." <199809200047.RAA21176@math.berkeley.edu> Date: Sat, 19 Sep 1998 18:32:37 -0700 Message-ID: <15339.906255157@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I fantasize that the problem is merely that someone recently installed > -current on current.freebsd.org and that I should accept this as a fair > warning. Well, to be fair, I upgraded it right at the time that CAM first entered the tree and it's more than likely that I am now bleeding from a bleeding-edge induced cut. If I can get the machine back up long enough to update its kernel, one hopes that it will work a little better. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message