On 11/9/07, Chris Frey <[EMAIL PROTECTED]> wrote: > On Fri, Nov 09, 2007 at 10:11:24AM +0100, Niels De Vos wrote: > > On 11/8/07, Chris Frey <[EMAIL PROTECTED]> wrote: > > > rmmod is not enough to prevent the conflict. You need to rename the > > > berry_charge module under /lib/modules before plugging in your device. > > > > Or add the following line to /etc/modprobe.conf: > > install berry_charge /bin/true > > > > This prevents modprobe loading the module. modprobe executes /bin/true > > instead. > > Thanks! That's so smooth, I'm tempted to put it right in the binary > package. That would save a lot of trouble.
Err, As far as I know, both of these solutions are hacks, and the proper way to do it would be to create a file like /etc/modprobe.d/blacklist-berry_charge containing: # conflicts with barry bcharge utility blacklist berry_charge ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
