on pathetic systems that haven't used a module to
configure and activate the tun module (see the tun DEB
and RPM), who also happen to have the tun module
compiled in as a module, the make-install script does
about one steop shy of causing the tun module to be
correctly loaded as required: the /etc/modules.conf
file will likely not have an entry for the tun module,
so that it is loaded on demand when the node
/dev/net/tun is first accessed.
If you want to cover this in your makefile - a brave
venture - then you will need to have code that:
- checks to see if the tun.o is as a module
- easiest way is to grep in /usr/src/linux/.config
- make sure to find it if [ ! -e ].
- inserts code into /etc/modules.conf
- rpm -qp --scripts /path/to/tun.rpm for example
- depmod -a
hey, this will be a good puzzle for you. I'll be
working around it because I'm building the RPM wirh a
requires: line requiring the tun RPM, the same way I'm
building OpenVPN and VTun RPMs, and it's so far worked
as a great workaround.
It just works, and that's the way it should be.
Logged In: YES
user_id=236673
Thanks, I'll look into this. The line for /etc/modules.conf
is given in the README file, but not incorporated into the
install script as there are several more problems with the
install script and I'm not brave enough at this time to
modify a user's modules.conf automagically.