It's nice to hear that it's not just me.
However, I don't see how this "resolution" works (at least for me (of course)).
When I attach the stick to the DSL VM (via the VMWare "VM -> Removable Devices -> Corsair Voyager [in my case] -> Connect",
VMWare is happy: it feels that the device is in fact connected to the guest O/S (DSL). The host O/S [Ubuntu, in my case] also
sees the stick "disappear," so all seems okay...
... but DSL does *NOT* see the device. fdisk shows only the VM's hard disk (which as we all know is really a file on the host O/S.
but that's irrelevant). parted doesn't seem to exist in DSL, so I can't run it on the guest O/S If I try running "fdisk /dev/sdc1", it sez
it's unable to open /dev/sdc1. If I run "fdisk -l /dev/sdc1", I get no output at all.
It might have to do with DSL kernel boot params, but I've tried a number of combinations there as well: with and without "scsi",
with and without "usb", etc.
And when the stick is connected to the host O/S. I do see that 1 MB pseudo-partition at the front of the stick. I am somewhat
reluctant to remove it and roll it into the partition forming the rest of the disk, for fear that there's something lurking there that
enables reading the whole stick.
Since the ultimate goal was just to create a SMALL Linux VM that could run a DNS server for my little virtual stand-alone network,
I'm now thinking I should bit the bullet and just move to a standard-sized Linux VM for the purpose. This seems to be my
typical "penny-wise and pound foolish" behavior: I've wasted too much time trying to make DSL do something it may just
not be able to do. Sigh...