I was curious about this statement, as I didn't believe it was true. So I grabbed the latest image off the repo, and looked at the partition table. This is what I found: Code: Model: (file) Disk mg-handset-armv7nhl-n900-ce-stable-1.2.0.90.6.20110630.4.DE.2011-07-01.1-mmcblk0p.raw: 3817MB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 512B 3775MB 3775MB primary ext4 2 3775MB 3783MB 8389kB primary linux-swap(v1) 3 3783MB 3817MB 33.6MB primary fat16 lba So yes, when you load the image on the eMMC it does overwrite the entire drive. But you're overwriting everything, including the partition table, with a new partition table contained in the image. This includes a swap volume in partition two. So, no bug.
Model: (file) Disk mg-handset-armv7nhl-n900-ce-stable-1.2.0.90.6.20110630.4.DE.2011-07-01.1-mmcblk0p.raw: 3817MB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 512B 3775MB 3775MB primary ext4 2 3775MB 3783MB 8389kB primary linux-swap(v1) 3 3783MB 3817MB 33.6MB primary fat16 lba
/dev/mmcblk0p1 / ext4 defaults,noatime 0 0 /dev/mmcblk0p3 /boot vfat defaults,noatime 0 0 /dev/mmcblk1p3 swap swap defaults,noatime 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 tmpfs /dev/shm tmpfs defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs defaults 0 0