From owner-freebsd-current Tue Jan 30 7: 5:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from hera.drwilco.net (10dyn62.dh.casema.net [212.64.31.62]) by hub.freebsd.org (Postfix) with ESMTP id ECC0537B491 for ; Tue, 30 Jan 2001 07:04:51 -0800 (PST) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.1/8.11.1) with ESMTP id f0UFQtb08138; Tue, 30 Jan 2001 16:26:57 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20010130160129.00aca700@mail.bsdchicks.com> X-Sender: lists@mail.bsdchicks.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 30 Jan 2001 16:03:10 +0100 To: Dag-Erling Smorgrav From: "Rogier R. Mulhuijzen" Subject: Re: stange console problem Cc: Chad David , freebsd-current@FreeBSD.ORG In-Reply-To: References: <"Rogier R. Mulhuijzen"'s message of "Tue, 30 Jan 2001 11:16:05 +0100"> <20010128221602.A88482@lodge.guild.ab.ca> <20010128221602.A88482@lodge.guild.ab.ca> <4.3.2.7.0.20010130110516.00cd1100@mail.bsdchicks.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >None of this has any bearing on the problem, which was caused by a bug >in gensetdefs.pl. Please update your source tree and rebuild your >kernel. Eek. I had the gensetdefs.pl problem too, but my machine just seemed to lock. He says his machine does go on running. I have been pretty tied up lately, so maybe I read his post a bit too quickly. DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message