search for: usb_drive

...are the same, and the level of support I get from RH is actually less effective and slower than resources such as this list, I'm looking here, first. Up to this point I was backing up to a USB-mounted external 1 TB hard drive. I was using a script containing: /sbin/dump -0v -z2 -f /media/usb_drive/dump0 /home I played with restore on that, and it tested fine. For the tape, I thought it would be nice to add /var/log (should have done it before, but didn't think of it...) Trying to adapt the knowledge to a tape library... /sbin/dump -0 -v -z2 -f /dev/nst0 /var/log /sbin/dump -0u -v -z...

...ght it was due to differences between Windows XP and 7 or different UPS models. But I'm noticing that it might be a bit more random than that. What does seem to always work is running wdi-simple.exe from the others folder manually. When having it run from the NUT installer, it will extract usb_driver to windows\system32 (or syswow64). And when run afterwards, the others folder instead. Not sure if that is really a problem or not except a bit messy. As always, thanks!

.... ...or if there's some reason that we don't need to do anything for those drivers then let me know and we can drop them. I'd like to call out a few drivers that I _didn't_ fix in this series and why. If any of these drivers should be fixed then please yell. - DRM drivers backed by usb_driver (like gud, gm12u320, udl): I didn't add the call to drm_atomic_helper_shutdown() at shutdown time because there's no ".shutdown" callback for them USB drivers. Given that USB is hotpluggable, I'm assuming that they are robust against this and the special shutdown call...

...ch series as RFT (request for testing) to help call attention to the fact that I didn't personally test any of these patches. I'd like to call out a few drivers that I _didn't_ fix in this series and why. If any of these drivers should be fixed then please yell. - DRM drivers backed by usb_driver (like gud, gm12u320, udl): I didn't add the call to drm_atomic_helper_shutdown() at shutdown time because there's no ".shutdown" callback for them USB drivers. Given that USB is hotpluggable, I'm assuming that they are robust against this and the special shutdown call...