From owner-freebsd-chat Tue Feb 4 11: 0:54 2003 Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BEAAD37B4B9 for ; Tue, 4 Feb 2003 11:00:45 -0800 (PST) Received: from hub.org (hub.org [64.49.215.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10CF344031 for ; Tue, 4 Feb 2003 10:53:17 -0800 (PST) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [64.49.215.141]) by hub.org (Postfix) with ESMTP id 0D5E38B5A61; Tue, 4 Feb 2003 14:52:19 -0400 (AST) Date: Tue, 4 Feb 2003 14:52:19 -0400 (AST) From: "Marc G. Fournier" To: Dag-Erling Smorgrav Cc: chat@freebsd.org Subject: Re: Good PR In-Reply-To: Message-ID: <20030204145121.X63349@hub.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Has anyone figured out what broken in recent FreeBSD releases (am running 4.7-STABLE right now) such that Netcraft can't even detect the OS anymore, let alone uptimes? http://uptime.netcraft.com/up/graph?host=jupiter.hub.org On Tue, 4 Feb 2003, Dag-Erling Smorgrav wrote: > These stats are good news for *BSDers: > > > > The only thing that worries me is that with an uptime that long, they > must be running a FreeBSD version with known security holes... > > DES > -- > Dag-Erling Smorgrav - des@ofug.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-chat" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message