Sonic McTails
13th May 2006, 08:00 PM
I used Boot Camp when it was first released to resize my parations and install Windows XP. My original drive configuration was this (this is a early 2006 MacBook Pro):
/dev/disk0
#: type name size identifier
0: GUID_partition_scheme *93.2 GB disk0
1: EFI 200.0 MB disk0s1
2: Apple_HFS Macintosh HD 67.0 GB disk0s2
3: Microsoft Basic Data WINDOWS XP 25.8 GB disk0s3
After a little experimentation, I issued the following command:
diskutil resizeVolume disk0s2 57G Linux "OpenSuSE" 10G
After a little time, I rebooted as per diskutils instructions, and when I rebooted, my new paration map is now:
/dev/disk0
#: type name size identifier
0: GUID_partition_scheme *93.2 GB disk0
1: EFI 200.0 MB disk0s1
2: Apple_HFS Macintosh HD 57.0 GB disk0s2
3: Microsoft Basic Data 10.0 GB disk0s3
4: Microsoft Basic Data WINDOWS XP 25.8 GB disk0s4
It appears that as long as resizeVolume command doesn't overlap the WinXP paration, you can safely add new parations. I haven't attempted to boot into Windows yet, but looking at the HD from Mac OS X, all my data appears to be intact.
/dev/disk0
#: type name size identifier
0: GUID_partition_scheme *93.2 GB disk0
1: EFI 200.0 MB disk0s1
2: Apple_HFS Macintosh HD 67.0 GB disk0s2
3: Microsoft Basic Data WINDOWS XP 25.8 GB disk0s3
After a little experimentation, I issued the following command:
diskutil resizeVolume disk0s2 57G Linux "OpenSuSE" 10G
After a little time, I rebooted as per diskutils instructions, and when I rebooted, my new paration map is now:
/dev/disk0
#: type name size identifier
0: GUID_partition_scheme *93.2 GB disk0
1: EFI 200.0 MB disk0s1
2: Apple_HFS Macintosh HD 57.0 GB disk0s2
3: Microsoft Basic Data 10.0 GB disk0s3
4: Microsoft Basic Data WINDOWS XP 25.8 GB disk0s4
It appears that as long as resizeVolume command doesn't overlap the WinXP paration, you can safely add new parations. I haven't attempted to boot into Windows yet, but looking at the HD from Mac OS X, all my data appears to be intact.