From owner-freebsd-current@FreeBSD.ORG Mon Aug 16 11:54:41 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4350016A4CE for ; Mon, 16 Aug 2004 11:54:41 +0000 (GMT) Received: from neerbosch.nijmegen.internl.net (neerbosch.nijmegen.internl.net [217.149.193.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EC3343D48 for ; Mon, 16 Aug 2004 11:54:40 +0000 (GMT) (envelope-from michiel@boland.org) Received: from brakkenstein.nijmegen.internl.net by neerbosch.nijmegen.internl.net id i7GBscYA014252 (8.12.10/1.4); Mon, 16 Aug 2004 13:54:38 +0200 (MET DST) Received: from localhost by brakkenstein.nijmegen.internl.net via mboland@localhost with ESMTP for id i7GBsbci004655 (8.12.10/2.02); Mon, 16 Aug 2004 13:54:37 +0200 (MEST) X-Authentication-Warning: brakkenstein.nijmegen.internl.net: mboland owned process doing -bs Date: Mon, 16 Aug 2004 13:54:37 +0200 (MEST) From: Michiel Boland To: current@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: sysinstall partition editor displays funny subtypes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Mon, 16 Aug 2004 11:54:41 -0000 Hi. I notice that the FDISK Partition Editor in sysinstall displays rather strange values for the partition types. For example, on a running -CURRENT (cvsupped last friday): Offset Size(ST) End Name PType Desc Subtype Flags 0 63 62 - 12 unused 0 63 78124032 78124094 ad0s1 4 unknown 0 78124095 905 78124999 - 12 unused 0 On my home machine a fresh install displayed the ad0s1 as "XENIX /usr" (subtype 3). What? :) I notice that fdisk displays the partition type ok. Here is the output from 'sysctl -b kern.geom.conftxt' 0 DISK ad0 40000000000 512 hd 16 sc 63 1 MBR ad0s1 39999504384 512 i 0 o 32256 2 BSD ad0s1f 38141648896 512 i 5 o 1857855488 2 BSD ad0s1e 268435456 512 i 4 o 1589420032 2 BSD ad0s1d 268435456 512 i 3 o 1320984576 2 BSD ad0s1c 39999504384 512 i 2 o 0 2 BSD ad0s1b 1052549120 512 i 1 o 268435456 2 BSD ad0s1a 268435456 512 i 0 o 0 Shouldn't there be a 'ty' entry for the MBR so that libdisk can populate the subtype member properly? Cheers Michiel