DragonFlyBSD

Sascha Wildner schrieb:

See this screenshot: http://yoyodyne.ath.cx/tmp/2009.08.15-21.43.22.bmp

Shorter jpeg here: http://yoyodyne.ath.cx/tmp/2009.08.15-21.43.22.jpg

Sascha

Try this:

fetch http://apollo.backplane.com/DFlyMisc/fd01.patch

It will be a little wonky but it should work.  /dev/fd0 and /dev/fd0a
    should show up permanently.  Other partitions/slices may show up
    if you fdisk/disklabel it, but only after you open() /dev/fd0 because
    the device driver does not detect floppy insertion and thus does not
    auto probe on floppy insertion.

-Matt
                    Matthew Dillon 
                    <dillon@backplane.com>

Matthew Dillon schrieb:

Try this:

fetch http://apollo.backplane.com/DFlyMisc/fd01.patch

It will be a little wonky but it should work. /dev/fd0 and /dev/fd0a
should show up permanently. Other partitions/slices may show up
if you fdisk/disklabel it, but only after you open() /dev/fd0 because
the device driver does not detect floppy insertion and thus does not
auto probe on floppy insertion.

Thanks, it fixes the panic and a quick test of tar'ing to/from the VM's
floppy works.

It does output "fd0: slice starts beyond end of the disk: rejecting it"
(4 times) and "fd0: Seek to cyl 0, but not really there (ST3 =
80<fault>)" messages.

If that can't be helped, I'd say commit it anyways.

Sascha