From owner-freebsd-current@FreeBSD.ORG Tue Jan 20 17:51:26 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 464781065677 for ; Tue, 20 Jan 2009 17:51:26 +0000 (UTC) (envelope-from a_best01@uni-muenster.de) Received: from zivm-out1.uni-muenster.de (ZIVM-OUT1.UNI-MUENSTER.DE [128.176.192.8]) by mx1.freebsd.org (Postfix) with ESMTP id CDEA48FC1E for ; Tue, 20 Jan 2009 17:51:25 +0000 (UTC) (envelope-from a_best01@uni-muenster.de) X-IronPort-AV: E=Sophos;i="4.37,295,1231110000"; d="scan'208";a="267481524" Received: from zivmaildisp1.uni-muenster.de (HELO ZIVMAILUSER01.UNI-MUENSTER.DE) ([128.176.188.85]) by zivm-relay1.uni-muenster.de with ESMTP; 20 Jan 2009 18:51:24 +0100 Received: by ZIVMAILUSER01.UNI-MUENSTER.DE (Postfix, from userid 149459) id C5DA01B0761; Tue, 20 Jan 2009 18:51:23 +0100 (CET) Date: Tue, 20 Jan 2009 18:51:23 +0100 (CET) From: Alexander Best Sender: Organization: Westfaelische Wilhelms-Universitaet Muenster To: Christoph Mallon Message-ID: In-Reply-To: <497577C3.4030602@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: fdisk: Class not found 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: Tue, 20 Jan 2009 17:51:26 -0000 nope. i'm getting the same error message using r187202. alex Christoph Mallon schrieb am 2009-01-20: > Alexander Best schrieb: > >when i'm trying to do the following: > >fdisk -B adX > >i get the following error message: > >fdisk: Class not found > >fdisk: Failed to write sector zero > >i'm running FreeBSD moshnroll 8.0-CURRENT FreeBSD 8.0-CURRENT #0 > >r187392M: Sun > >Jan 18 14:42:30 UTC 2009 > >root@moshnroll:/usr/obj/usr/src/sys/ARUNDEL i386 > >and rebuild and reinstalled fdisk. > Does this also happen with fdisk of revision r187202? The changes > after that should be harmless, but I want to play it safe. Just > updating sbin/fdisk to this revision and rebuilding it is sufficient > to test this. > Christoph