SEO

#1 (**permalink**) 02-21-2008, 04:37 AM

Hello!
I have here a box running Slackware 11.0. He/it has the 2.6.18 kernel
installed as created by the people at Slackware itself.

Now every time I insert a USB fob made by Maxim/Dallas Semiconductor
for their One-Wire technology parts, the OS immediately wants to
install the modules it believes people actually use for this device.
According to the maintainer at the time of the kernel release he
wasn't even aware that an example of software did exist, its available
at http://owfs.sf.net . Now that's what I use. Problem is that these
modules are not supposed to be loaded. (Two of the people behind the
software development cycle did indeed communicate with the maintainer,
needless to say these discussions went no place special.)

Does anyone have any suggestions for what rules to setup to prevent
this from happening?
---
Gregg gregg.drwho8@gmail.com (Who cares about spam?)
System uptime is 1 day plus 4:04, and the registered Linux Counter
entry number is #173298, and that update script is there

#2 (**permalink**) 02-21-2008, 04:37 AM

On 2007-10-08, gregg dot drwho8 atsign gmail dot com <gregg.drwho8@gmail.com> wrote:
> Hello!
> I have here a box running Slackware 11.0. He/it has the 2.6.18 kernel
> installed as created by the people at Slackware itself.
>
> Now every time I insert a USB fob made by Maxim/Dallas Semiconductor
> for their One-Wire technology parts, the OS immediately wants to
> install the modules it believes people actually use for this device.
> According to the maintainer at the time of the kernel release he
> wasn't even aware that an example of software did exist, its available
> at http://owfs.sf.net . Now that's what I use. Problem is that these
> modules are not supposed to be loaded. (Two of the people behind the
> software development cycle did indeed communicate with the maintainer,
> needless to say these discussions went no place special.)
>
> Does anyone have any suggestions for what rules to setup to prevent
> this from happening?

Hmmm... don't have any Slack 11.0 lying around anymore, but is there a
file /etc/modprobe.d/blacklist? If so, what happens if you put
blacklist <the-module-you-don't-want-autoloaded>
in there? (Then run depmod.)

Jim

#3 (**permalink**) 02-21-2008, 04:37 AM

Jim Diamond wrote:
> On 2007-10-08, gregg dot drwho8 atsign gmail dot com <gregg.drwho8@gmail.com> wrote:
> > Hello!
> > I have here a box running Slackware 11.0. He/it has the 2.6.18 kernel
> > installed as created by the people at Slackware itself.
> >
> > Now every time I insert a USB fob made by Maxim/Dallas Semiconductor
> > for their One-Wire technology parts, the OS immediately wants to
> > install the modules it believes people actually use for this device.
> > According to the maintainer at the time of the kernel release he
> > wasn't even aware that an example of software did exist, its available
> > at http://owfs.sf.net . Now that's what I use. Problem is that these
> > modules are not supposed to be loaded. (Two of the people behind the
> > software development cycle did indeed communicate with the maintainer,
> > needless to say these discussions went no place special.)
> >
> > Does anyone have any suggestions for what rules to setup to prevent
> > this from happening?
>
>
> Hmmm... don't have any Slack 11.0 lying around anymore, but is there a
> file /etc/modprobe.d/blacklist? If so, what happens if you put
> blacklist <the-module-you-don't-want-autoloaded>
> in there? (Then run depmod.)
>
> Jim

Hello!
Problem solved. I did at first examine and create the blacklist
entries, but ah, I had a "senior moment" there. I actually put down
the device name rather then the name of the part that the module is
named after. I just changed the name accordingly. It works as
advertised.
---
Gregg gregg.drwho8@gmail.com

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

USB device and module issues