From owner-freebsd-current@FreeBSD.ORG Sun Apr 19 12:00:03 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 063D41065672 for ; Sun, 19 Apr 2009 12:00:02 +0000 (UTC) (envelope-from ubm@u-boot-man.de) Received: from mail.upper.net (mail.upper.net [62.75.224.33]) by mx1.freebsd.org (Postfix) with ESMTP id 8E3258FC13 for ; Sun, 19 Apr 2009 12:00:02 +0000 (UTC) (envelope-from ubm@u-boot-man.de) Received: from ubm.mine.nu (mail.upper.net [62.75.224.33]) (authenticated bits=0) by mail.upper.net (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id n3JBg5B9025433 for ; Sun, 19 Apr 2009 13:42:05 +0200 Received: from ubm.mine.nu ([85.181.44.8] helo=ubm.mine.nu) by ASSP.nospam.UpPeRnEt; 19 Apr 2009 13:42:05 +0200 Date: Sun, 19 Apr 2009 13:42:04 +0200 From: Marc "UBM" Bocklet To: freebsd-current@freebsd.org Message-Id: <20090419134204.57ad25a7.ubm@u-boot-man.de> X-Mailer: Sylpheed 2.6.0 (GTK+ 2.12.10; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sun, 19 Apr 2009 12:07:01 +0000 Subject: minor annoyance with usb transition (or pilot error) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Apr 2009 12:00:03 -0000 Hiho! :-) I'm in the process of upgrading to the latest -current (I'm currently running -current as of 02. Jan. 2009). I was using the new usb stack with the 02. Jan. -current and consequently had to change my kernel config back to the old usb naming scheme (after changing to the temporary new usb naming scheme in January). While doing this, "device ugen" caused my kernconf to fail, I had to comment it out. Including "device udbp" makes buildkernel fail (I can reproduce this and post the error, but I believe this is known). I was wondering if UPDATING should mention that device ugen is no longer needed (if thats the case), else people using their old kernel config will have it fail until they comment "device ugen" out. Of course, all this might also just be some stupid mistake on my part? :-) Greetings, Marc -- "And what rough beast, its hour come round at last, Slouches towards Bethlehem to be born?" W.B. Yeats, The Second Coming