At Mon, 11 Jun 2007 13:12:04 -0700,
Chuck Swiger wrote:
If you ever use it, fdisk /dev/rdisk0 will show things differently.
The first partition with id 0xEE will should start at LBA 40 and end
at LBA 409640.
OK: although that surprises me a bit, perhaps trying to get Windows
XP (which
Matthew Dillon wrote:
It really sounds like they are making an accomodation for BIOS
booting or older Windows booting... or *something* of that sort. The
fact that the bootability bit is not set in the MBR (I'm not sure about
that, is it set or not?)... that seems to imply a
At Mon, 11 Jun 2007 13:33:42 -0700 (PDT),
Matthew Dillon wrote:
: # gpt -r show /dev/rdisk0
:start size index contents
:0 1 PMBR
:1 1 Pri GPT header
:2 32 Pri GPT table
: 34
At Mon, 11 Jun 2007 12:41:18 -0700,
Chuck Swiger wrote:
Hi, all--
On Jun 10, 2007, at 3:13 PM, Rui Paulo wrote:
:Media sector size is 512
:Warning: BIOS sector numbering starts with sector 1
:Information from DOS bootblock is:
:The data for partition 1 is:
:sysid 238 (0xee),(EFI
At Sun, 10 Jun 2007 23:13:59 +0100,
Rui Paulo wrote:
At Sun, 10 Jun 2007 14:43:26 -0700 (PDT),
Matthew Dillon wrote:
:No.
:The first partition is the EFI GPT (0xee):
:
:% fdisk -1
:*** Working on device /dev/ad0 ***
:...
:parameters to be used for BIOS calculations
Hi, all--
On Jun 10, 2007, at 3:13 PM, Rui Paulo wrote:
:Media sector size is 512
:Warning: BIOS sector numbering starts with sector 1
:Information from DOS bootblock is:
:The data for partition 1 is:
:sysid 238 (0xee),(EFI GPT)
:start 40, size 409600 (200 Meg), flag 0
:beg: cyl 0/
On Jun 11, 2007, at 12:52 PM, Rui Paulo wrote:
A typical Intel Mac system using GPT ought to look something like
this:
# fdisk /dev/rdisk0
Disk: /dev/rdisk0 geometry: 9964/255/63 [160086528 sectors]
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [
: # gpt -r show /dev/rdisk0
:start size index contents
:0 1 PMBR
:1 1 Pri GPT header
:2 32 Pri GPT table
: 34 6
: 40 409600 1 GPT part -
:Technically speaking, the MBR can only have a single partition of
:type 0xEE that covers the whole disk. This is to protect the GPT
:from MBR-specific tools that do not know about the GPT. This is
:not a bootable slice by definition.
:
:Practice is different. To support bootcamp on Intel-based
On Jun 10, 2007, at 10:52 AM, Matthew Dillon wrote:
:Technically speaking, the MBR can only have a single partition of
:type 0xEE that covers the whole disk. This is to protect the GPT
:from MBR-specific tools that do not know about the GPT. This is
:not a bootable slice by definition.
:
:No.
:The first partition is the EFI GPT (0xee):
:
:% fdisk -1
:*** Working on device /dev/ad0 ***
:...
:parameters to be used for BIOS calculations are:
:cylinders=116280 heads=16 sectors/track=63 (1008 blks/cyl)
:
:Media sector size is 512
:Warning: BIOS sector numbering starts with
At Sun, 10 Jun 2007 11:08:47 -0700,
Marcel Moolenaar wrote:
On Jun 10, 2007, at 10:52 AM, Matthew Dillon wrote:
:Technically speaking, the MBR can only have a single partition of
:type 0xEE that covers the whole disk. This is to protect the GPT
:from MBR-specific tools that do not
At Sun, 10 Jun 2007 14:43:26 -0700 (PDT),
Matthew Dillon wrote:
:No.
:The first partition is the EFI GPT (0xee):
:
:% fdisk -1
:*** Working on device /dev/ad0 ***
:...
:parameters to be used for BIOS calculations are:
:cylinders=116280 heads=16 sectors/track=63 (1008 blks/cyl)
On Jun 9, 2007, at 9:22 AM, Ivan Voras wrote:
Another thing that would be nice to have is support for fdisk and
disklabel partitions inside geom_part, so it's management utility
can be
used for both GPT and old style partition management (instead of
currently used two tools: fdisk and
On Jun 9, 2007, at 1:04 PM, Ivan Voras wrote:
Marcel Moolenaar wrote:
On Jun 9, 2007, at 9:22 AM, Ivan Voras wrote:
Another thing that would be nice to have is support for fdisk and
disklabel partitions inside geom_part, so it's management utility
can be
used for both GPT and old style
I'm having to tackle this issue right now in DFly. With GPT having to
start at sector 1 (no choice there), the compatible MBR in sector 0
presumably must have a slice (#1) which covers the entire disk.
But do we have to make slice #1 bootable? Could we also create a
slice #2
On Jun 9, 2007, at 2:28 PM, Matthew Dillon wrote:
I'm having to tackle this issue right now in DFly. With GPT
having to
start at sector 1 (no choice there), the compatible MBR in
sector 0
presumably must have a slice (#1) which covers the entire disk.
But do we have to
17 matches
Mail list logo
