[Nook Color Android Development] pezhore:
Ran the v0.2 script and below is the output. Part of the problem may be that the dualboot folder ended up on /media/ rather than /sdcard (/sdcard/ was empty).

/media/dualboot # sh dual-boot.sh
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>Create working directory
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>Back up /media to sdcard
>>>>>>>>>>>>>>>>>>>>
tar: removing leading '/' from member names
umount: can't umount /media: Device or resource busy
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>We delete partition 9 a few times
>>>>>>>>>>>>>>>>>>>>to make sure there is no Froyo
>>>>>>>>>>>>>>>>>>>>partition left. You can ignore
>>>>>>>>>>>>>>>>>>>>the message - Error: Partition doesn't exist
>>>>>>>>>>>>>>>>>>>>
Error: Partition doesn't exist.
Error: Partition doesn't exist.
Error: Partition doesn't exist.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>Move and resize media partition
>>>>>>>>>>>>>>>>>>>>
Error: Partition /dev/block/mmcblk0p8 is being used. You must unmount it before you modify it with Parted.
Error: Can't have overlapping partitions.
warning, /dev/block/mmcblk0p8 is not a character device
Skipping mount checks
trim 15 sectors to adjust to a multiple of 16
/dev/block/mmcblk0p8: 10503808 sectors in 164122 FAT32 clusters (32768 bytes/cluster)
bps=512 spc=64 res=32 nft=2 mid=0xf0 spt=16 hds=4 hid=0 bsec=10506432 bspf=1283 rdcl=2 infs=1 bkbs=2
mount: mounting /dev/block/mmcblk0p8 on /media failed: Device or resource busy
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>Restore /media
>>>>>>>>>>>>>>>>>>>>
tar: can't open 'media/LOST.DIR/3928': Read-only file system
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>Create Froyo system and data partition
>>>>>>>>>>>>>>>>>>>>
Error: You requested a partition from 2311MB to 2681MB.
The closest location we can manage is 2311MB to 2311MB.
Error: Can't have overlapping partitions.
mke2fs 1.40.8 (13-Mar-2008)
Could not stat /dev/block/mmcblk0p9 --- No such file or directory

The device apparently does not exist; did you specify it correctly?
tune2fs 1.40.8 (13-Mar-2008)
tune2fs: No such file or directory while trying to open /dev/block/mmcblk0p9
Couldn't find valid filesystem superblock.
mke2fs 1.40.8 (13-Mar-2008)
Could not stat /dev/block/mmcblk0p10 --- No such file or directory

The device apparently does not exist; did you specify it correctly?
tune2fs 1.40.8 (13-Mar-2008)
tune2fs: No such file or directory while trying to open /dev/block/mmcblk0p10
Couldn't find valid filesystem superblock.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>Copy Nookie Froyo files
>>>>>>>>>>>>>>>>>>>>
mount: mounting /dev/block/mmcblk0p9 on /data/dualboottmp/system failed: No such file or directory
mount: mounting /dev/block/mmcblk0p10 on /data/dualboottmp/data failed: No such file or directory
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>Clean up
>>>>>>>>>>>>>>>>>>>>
umount: can't umount /data/dualboottmp/system: Invalid argument
umount: can't umount /data/dualboottmp/data: Invalid argument
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>Done
>>>>>>>>>>>>>>>>>>>>

At this point, I'd guess I am partially screwed. Thoughts on why this may have failed to work? I'm guessing it stems from partition /dev/block/mmcblk0p8 being mounted prior to the parted actions.