This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: Libusb-win32-0.1.12.1-1 makes system unusable after reboot.
- From: Samuel Thibault <samuel dot thibault at ens-lyon dot org>
- To: Ton van Overbeek <ton at v-overbeek dot nl>
- Cc: cygwin at cygwin dot com, cygwin-apps at cygwin dot com
- Date: Sat, 24 Mar 2007 20:21:06 +0100
- Subject: Re: Libusb-win32-0.1.12.1-1 makes system unusable after reboot.
- References: <20070324151544.GA3541@interface.famille.thibault.fr> <20070324200659.X11058-100000@xs2.xs4all.nl>
Ton van Overbeek, le Sat 24 Mar 2007 20:13:21 +0100, a écrit :
> > Err, no, usbd.sys is always installed in
> > c:\windows\system32\drivers\usbd.sys, and that's precisely because
> > libusb0.sys is not installed there too that the usual discovery fails.
> >
>
> Yes, I know. But copying usbd.sys to /usr/lib/libusb makes the problem
> go away.
Well, yes, but usbd.sys definitely belongs to windows/system32/drivers.
Remember that this is a windows-shipped file, we shouldn't make a copy
like this.
> > Actually, I'm wondering: instead of trying to make libusb0.sys work
> > from /usr/lib/libusb/, is it fine (packaging-wise, I mean), in
> > libusb-install, to just copy it into c:\windows\system32\drivers\ and
> > then use the usual libusb-win32 filter setup? That works fine and
> > actually makes the patch simpler...
> >
>
> I am pretty sure that would solve the problem.
Yes it does, but the question to cygwin developers is: is it ok
packaging-wise?
Samuel