Messages in this thread | | | Subject | A module bug in 2.2.1? | Date | Thu, 04 Feb 1999 11:20:06 -0500 | From | Justin Hahn <> |
| |
> I just tried "modprobe -s an_unknown_module", and indeed it > does try to log the failed request for an unknown module via syslog. > If you already have that net-pf-1 line in your /etc/conf.module, you > might want to try this: > > mv /sbin/modprobe /sbin/modprobe.real > cat > /sbin/modprobe << EOF > #!/bin/sh > echo "$*" >> /tmp/modprobe.log > EOF > reboot > > This will put a list of the modules that the kernel is > tring to load in /tmp/modprobe.log.
And reboot everytime you try to load a module. Like say, on boot? Not exactly what I'd call a good idea.
----------------------------------------------- Justin Hahn <jehahn@raven.bu.edu> Systems Administrator Boston University SPI Lab -----------------------------------------------
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |