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.
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
# 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
--
--- 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?
4 matches
Mail list logo
