From owner-freebsd-geom@FreeBSD.ORG Mon Jan 19 14:37:43 2015 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 35F81A89; Mon, 19 Jan 2015 14:37:43 +0000 (UTC) Received: from forward7l.mail.yandex.net (forward7l.mail.yandex.net [IPv6:2a02:6b8:0:1819::7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E2624657; Mon, 19 Jan 2015 14:37:42 +0000 (UTC) Received: from smtp18.mail.yandex.net (smtp18.mail.yandex.net [95.108.252.18]) by forward7l.mail.yandex.net (Yandex) with ESMTP id 356E9BC1114; Mon, 19 Jan 2015 17:37:40 +0300 (MSK) Received: from smtp18.mail.yandex.net (localhost [127.0.0.1]) by smtp18.mail.yandex.net (Yandex) with ESMTP id A344C18A00E7; Mon, 19 Jan 2015 17:37:39 +0300 (MSK) Received: from unknown (unknown [2a02:6b8:0:1495::f3]) by smtp18.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 4LTab20PuZ-bdDK1omg; Mon, 19 Jan 2015 17:37:39 +0300 (using TLSv1.2 with cipher AES128-SHA (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1421678259; bh=JDPAZ8TOE/CLcNhWokvMBSc5VPt6avCQ+oKvLWXWbMw=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:Subject: References:In-Reply-To:Content-Type; b=K831W+4t2d7uQIEiBJz9uq5D2c6ElP61Tiahl69J69G0vyc1xc7cvBVn1lRDvyYJR hmt690qz1GLaU4a+FJluLd+8ZPlSyQ++pEI5p3OvCZPkZ8BxdySKzHszAKPR3d2H/D /91Uwzdop0ustGcTre0o/EufsMfKSXK2ZuUwPy5c= Authentication-Results: smtp18.mail.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <54BD165D.60105@yandex.ru> Date: Mon, 19 Jan 2015 17:36:13 +0300 From: "Andrey V. Elsukov" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: lev@FreeBSD.org, 'freebsd-geom' Subject: Re: gpart: add MBR type !133 (0x85) as alias for EBR (type !5)? References: <54BC1F19.3030109@FreeBSD.org> In-Reply-To: <54BC1F19.3030109@FreeBSD.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ehTRR5BFM0fmWIGNqa0naa0N0b1LgS1Sw" X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jan 2015 14:37:43 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --ehTRR5BFM0fmWIGNqa0naa0N0b1LgS1Sw Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 19.01.2015 00:01, Lev Serebryakov wrote: >=20 > What do you think about $subj? > Ive encountered several disks which have partition with type 133 and > it it valid EBR, as if it has type 5. >=20 > Wikipedia says, that it is (was?) used by Linux. Also it says, that this type is used for second extended partition chain. This means you can not just add type id to MBR scheme, because this will lead to partition names collisions in GEOM_PART_EBR_COMPAT mode. Anyway we don't handle this correctly, even if you will use 0x05/0x0f for second chain :) --=20 WBR, Andrey V. Elsukov --ehTRR5BFM0fmWIGNqa0naa0N0b1LgS1Sw Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJUvRZdAAoJEAHF6gQQyKF6Qq8H/1strap9xStNMPouml6yKJjw xWcPlDFxrqd6CXGzx7vNs4e4hA2R/iJPAhtaVbqNcLxdUPDPl+jF78pyVM/CApBn NtL/6rmm22BV7BTIYkoUYmJt1fSuGxX74iiGnLhLuRCMTLnczSQfK21ki/Tat1gd THofTtPUpY5Bs5SJytYxcFU6rP/rpAEqStR7eKbAPNrWCTzpQ/eYPX2SXoTAVnji oDThDGRMRiSzfmWKuXB2idvK1MqC2TQm9cdpg5GnEa0+XbWks+9Th7CGOemMsDNg mBYhQYJMBLKH5xt+6KiaH9R0rjjTKVWkzbxWo72sobfF9bXnAIWO/J0C+DObru8= =jmA4 -----END PGP SIGNATURE----- --ehTRR5BFM0fmWIGNqa0naa0N0b1LgS1Sw--