SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Answering because no answers for many days, not because I'm an expert ...
The rule means:
DRIVER==usbtest Apply this rule to all devices which the kernel chooses to use the usbtest driver for.
RUN+= Add the following command to commands to be run for this device (will be ineffective if there is a subsequent RUN=).
"/bin/sh -c '...'" Run /bin/sh, telling it to execute the command in single quotes.
echo -n %k> %S%p/driver/unbind Write the kernel name for this device to /sys/<path for this device>/driver/unbind. That explanation is based on the udev man page documentation of %* "substitutions" and may well not be exactly right. Maybe %S is /proc, not /sys.
The meaning of the first two lines of quoted dmesg depends on the usbtest driver itself. The third presumably means the usbtest driver has been added/loaded within the USB drivers framework.
Distribution: slack 7.1 till latest and -current, LFS
Posts: 368
Rep:
hi PeterUK, the Warning is a warning.
It basicaly means that you compile the code against another program that has released a newer version.
In this newer version they are using '__xdata' instead of 'xdata'
so the program you are compiling is basically written against an older version of the dependency.
and do not worry it is a warning, and not an error.
hi PeterUK, the Warning is a warning.
It basicaly means that you compile the code against another program that has released a newer version.
In this newer version they are using '__xdata' instead of 'xdata'
so the program you are compiling is basically written against an older version of the dependency.
and do not worry it is a warning, and not an error.
Compilers emit warnings for errors that aren't so bad that the compiler cannot continue. You should fully understand what the warning means before you hand wave it away as a "no biggie."
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.