delorie.com/archives/browse.cgi | search |
Date: | Sat, 21 Jul 2001 08:26:17 +0100 (BST) |
To: | Matthias Paul <Matthias DOT Paul AT post DOT rwth-aachen DOT de> |
cc: | <fd-dev AT topica DOT com>, <opendos AT delorie DOT com> |
Subject: | Re: [fd-dev] Proposal for new partition type IDs for use with future |
DOSes | |
In-Reply-To: | <0.1300007563.1860321608-951758591-991179339@topica.com> |
Organization: | Mayday Technology Ltd |
X-URL: | <http://www.cix.co.uk/~mayday> |
X-Dev86-Version: | 0.16.0 |
MIME-Version: | 1.0 |
From: | Robert de Bath <robert$@mayday.cix.co.uk> |
Message-ID: | <2e7d3d57ffe21392@mayday.cix.co.uk> |
X-Mailer: | Pine for Linux |
Reply-To: | opendos AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | opendos AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
I've just done a bit of catchup on fd-dev and noticed that nobody in this thread mentioned partition type 0x85, the Linux extended partition container. The Linux kernel treats 0x05, 0x0F and 0x85 identically allowing multiple extended partitions in the MBR and one extended and/or upto four data partitions in each extended partition. There only reason for the 0x85 partition to exist was that at the time no M$ OS could access sectors beyond the CHS limits. (The bios extensions didn't exist either) Nowadays putting an 0x85 in partition 1 is a good way of protecting partitions from M$ corruption as M$ would never follow Linux's lead ... :-) -- Rob. (Robert de Bath <robert$ @ debath.co.uk>) <http://www.cix.co.uk/~mayday>
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |