Package: gnu-fdisk Version: 1.0-3+b1 Severity: grave Justification: causes non-serious data loss
gnu-fdisk wipes out the Code Area in the MBR of a given device when modifying a GPT partition. If this happens to be the boot device, this can cause serious trouble. The behaviour can be easily verified with dd and hexdump. Create a blockdevice with a gpt label, then write data to the code area, e.g.: dd if=/dev/urandom of=/dev/sdc bs=440 count=1 and verify that it's there: dd if=/dev/sdc bs=512 count=1 | hexdump -C -v Then get fdisk to rewrite the partition table (starting and immediately (re)writing the partition table works); a verification with dd/hexdump should show an empty Code Area. The free encyclopedia has a nice layout of the MBR, for verification: http://en.wikipedia.org/wiki/Master_boot_record best regards, Michael -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gnu-fdisk depends on: ii libc6 2.7-15 GNU C Library: Shared libraries ii libncurses5 5.6+20080830-1 shared libraries for terminal hand ii libparted1.8-10 1.8.8.git.2008.03.24-11 The GNU Parted disk partitioning s ii libuuid1 1.41.2-1 universally unique id library gnu-fdisk recommends no packages. gnu-fdisk suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
