Re: insmod tun fails. modprobe tun succeeds.
On Sun, 7 Sep 2003 01:33:43 +0200 (CEST), Roberto Sanchez wrote: No bug, just the behavior of the program. You probably want to stick to modprobe anyway. Turns out that with the version of insmod that is for kernels 2.5.48 and above, one should either specify the path or use modprobe. The reference for this is at http://bugs.debian.org/209702. -- Shaul Karl,shaulk @ actcom . net . il -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: insmod tun fails. modprobe tun succeeds.
On Sun, Sep 07, 2003 at 01:33:43AM +0200, Roberto Sanchez wrote: From the modprobe man page: Modprobe will automatically load all base modules needed in a module stack, as described by the dependency file modules.dep. Basically, modprobe automatically resolves module dependencies based on the current modules.dep. $ grep tun /lib/modules/2.6.0-test2.custom586.1/modules.dep /lib/modules/2.6.0-test2.custom586.1/kernel/drivers/net/tun.ko: $ I am still not convinced there is no bug. -- Shaul Karl,shaulk @ actcom . net . il -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
insmod tun fails. modprobe tun succeeds.
# insmod tun Can't open 'tun': No such file or directory # lsmod |grep tun # modprobe tun # lsmod |grep tun tun 7776 0 And /dev/net/tun do exists. Am I doing something wrong or is it a bug? -- Shaul Karl,shaulk @ actcom . net . il -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: insmod tun fails. modprobe tun succeeds.
--- Shaul Karl [EMAIL PROTECTED] escribió: # insmod tun Can't open 'tun': No such file or directory # lsmod |grep tun # modprobe tun # lsmod |grep tun tun 7776 0 And /dev/net/tun do exists. Am I doing something wrong or is it a bug? From the modprobe man page: Modprobe will automatically load all base modules needed in a module stack, as described by the dependency file modules.dep. If the loading of one of these modules fails, the whole current stack of modules loaded in the current session will be unloaded automatically. Basically, modprobe automatically resolves module dependencies based on the current modules.dep. Insmod only tries to insert the named module and fails if the dependencies are not already met. No bug, just the behavior of the program. You probably want to stick to modprobe anyway. -Roberto ___ Yahoo! Messenger - Nueva versión GRATIS Super Webcam, voz, caritas animadas, y más... http://messenger.yahoo.es -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]