From owner-freebsd-current Thu Apr 9 00:30:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA15137 for freebsd-current-outgoing; Thu, 9 Apr 1998 00:30:13 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA15128 for ; Thu, 9 Apr 1998 00:30:08 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id JAA05122; Thu, 9 Apr 1998 09:28:58 +0200 (CEST) To: "Daniel O'Connor" cc: Greg Lehey , FreeBSD current users Subject: Re: Any big problems with -CURRENT at the moment? In-reply-to: Your message of "Thu, 09 Apr 1998 11:17:55 +0930." <199804090147.LAA29494@cain.gsoft.com.au> Date: Thu, 09 Apr 1998 09:28:58 +0200 Message-ID: <5120.892106938@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199804090147.LAA29494@cain.gsoft.com.au>, "Daniel O'Connor" writes: > >> I'm planning to upgrade my machine to the latest -CURRENT. In view of >> the problems we've been having lately, I'd like to ask if there are >> any to be expected at the moment. The mailing list seems relatively >> quiet. >Well, it seems OK, except that nanosleep() doesn't work for me, but no-one >else seems to get it.. Last I heard from you you were not running -current sources... >Also the fact that I can't run config on my kernel config is kind of annoying >, >but no-one else seems to be getting these problems, so it could just be me.. post a testcase program and lets test it... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message