Background: https://github.com/grml/grml/issues/205 Using fdisk 2.36.1-8+deb11u1 from util-linux to create an extra partition on a USB stick on which I had previously written an ISO 9660 image does something to the data on the stick to make klibc fstype not recognise it as ISO 9660 any more. Specifically, it corrupts some data at some location within the first 4 MiB of the stick but outside of the first 512 byte of it, as restoring those first 4 MiB then re-restoring the MBR to the state fdisk had written makes it work again. This is a data corruption bug. I expect fdisk to change precisely the MBR and nothing else unless told so. Is there a way we can make it not corrupt such media? Thanks in advance, //mirabilos -- 08:05⎜<XTaran:#grml> mika: Does grml have an tool to read Apple ⎜ System Log (asl) files? :) 08:08⎜<ft:#grml> yeah. /bin/rm. ;) 08:09⎜<mrud:#grml> hexdump -C 08:31⎜<XTaran:#grml> ft, mrud: *g*
