4 ms·
Doesn't mention what hypervisor is used (qemu? bochs?) but if it speaks NBD then you can do: $ nbdkit floppy /path/to/some/directory which will serve the da
by rwmj 2y ago
Doesn't mention what hypervisor is used (qemu? bochs?) but if it speaks NBD then you can do:
$ nbdkit floppy /path/to/some/directory
which will serve the data in that directory as a floppy disk over NBD on port 10809. In qemu you can attach this with -drive nbd:localhost:10809.
It doesn't use mkfs.fat, instead a custom FAT generator, and I think people have used it with ancient guests (however I'd have to check to be sure, either way should be easy to patch).
- blueflow 2y agoDoes nbdkit generate the correct OEM Label value? I don't believe so.
- rwmj 2y agoI thought someone had sent me a fix for this in the distant past, but I can't find the "MSDOSxxx" label in the source. However the custom generator should be easy to fix: https://gitlab.com/nbdkit/nbdkit/-/blob/a2fe619c45a97fd89063cc8d9106264c5adf6018/plugins/floppy/virtual-floppy.c#L454 https://gitlab.com/nbdkit/nbdkit/-/blob/a2fe619c45a97fd89063... However one definite restriction is it only serves FAT32 (not FAT16), which would be a dealbreaker for really old guests like this.
- blueflow 2y agoOS/2 2.1 (1993) cannot support FAT32 (1996) as it predates it.