Thomas Weißschuh dixit: > The device contains 'iso9660' signature and it will be removed by a > write command. See fdisk(8) man page and --wipe option for more > details. >I guess your version does the same, but maybe is not printing the >warning. Hm, maybe it does, maybe it doesn’t, but even so, why should it? >So the disk gets converted to a normal MBR layout and the ISO signature >get wiped. Which makes sense as the ISO image would need to be >remastered. Totally not! First of, the ISO already contained an MBR with a partition table in the first sector, which I extended, and second, it’s fdisk’s task to precisely edit the MBR partition table (and, if the 55h AAh magic is missing, create it), nothing else (okay, extended partitions if someone uses them, but nothing else). >> Is there a way we can make it not corrupt such media? > >Did you look into grml2usb? I know that, but I wanted to keep the original ISO 9660 filesystem so things don’t accidentally get changed on it. (And the original EFI thingy, in case it’s needed.) So, how do I get fdisk to not corrupt the ISO 9660 part? MirBSD fdisk doesn’t do that, it sticks to the MBR. Thanks, //mirabilos -- „Cool, /usr/share/doc/mksh/examples/uhr.gz ist ja ein Grund, mksh auf jedem System zu installieren.“ -- XTaran auf der OpenRheinRuhr, ganz begeistert (EN: “[…]uhr.gz is a reason to install mksh on every system.”)
