Hi Folks
at 11.10.2012 16:32, Andrew wrote:
modules.dep is re-generated at kmodules package in main branch; in 4.x
branch it seems that depmod isn't called at all.
Why you don't want to use module auto-probing which should load modules
that are specified in /etc/modules? Or this is remote
12.10.2012 12:51, Erich Titl пишет:
Hi Folks
at 11.10.2012 16:32, Andrew wrote:
modules.dep is re-generated at kmodules package in main branch; in 4.x
branch it seems that depmod isn't called at all.
Why you don't want to use module auto-probing which should load modules
that are specified
Hi Folks
I am about to test OpenSWan on BuC 4.3.
It looks like the modules.dep file does not contain a reference to
ipsec.ko, so I looked in the corresponding directory in staging and
indeed modules.dep is not updated.
Does anyone know where we run depmod, so it can be called in the
openswan
Le 11/10/2012 14:25, Erich Titl a écrit :
Hi Folks
I am about to test OpenSWan on BuC 4.3.
It looks like the modules.dep file does not contain a reference to
ipsec.ko, so I looked in the corresponding directory in staging and
indeed modules.dep is not updated.
Does anyone know where we
Hi Yves
at 11.10.2012 16:02, Yves Blusseau wrote:
Le 11/10/2012 14:25, Erich Titl a écrit :
Hi Folks
I am about to test OpenSWan on BuC 4.3.
It looks like the modules.dep file does not contain a reference to
ipsec.ko, so I looked in the corresponding directory in staging and
indeed
Am 11.10.2012 16:18, schrieb Erich Titl:
Hi Yves
at 11.10.2012 16:02, Yves Blusseau wrote:
Le 11/10/2012 14:25, Erich Titl a écrit :
Hi Folks
I am about to test OpenSWan on BuC 4.3.
It looks like the modules.dep file does not contain a reference to
ipsec.ko, so I looked in the
modules.dep is re-generated at kmodules package in main branch; in 4.x
branch it seems that depmod isn't called at all.
Why you don't want to use module auto-probing which should load modules
that are specified in /etc/modules? Or this is remote box that will be
unavailable w/o ipsec.ko?
On
