Re: [leaf-devel] updating modules.dep
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 in /etc/modules? Or this is remote box that will be >> unavailable w/o ipsec.ko? > Reading makefiles is tedious, after all they are meant to be interpreted > by machines, not human beings. > > depmod is done at modules_install in the kernel makefile. > > The easiest way to regenerate the file is to re-run depmod once the > ipsec.ko module is copied to the STAGINg area. Now doing this, the full > tree names of the modules are written to the modules.dep file instead of > the flat hierarchy used in 4.x. Somewhere this must be stripped. > > Now what puzzles me is that the build destination for most stuff is not > the staging area but the build directory. It appears also that depmod is > run against the modules in build and not against the modules in staging. > > Could someone enlighten me about the reasoning for the two different areas? > > Thanks > > Erich > Look at kmodules package into master branch. Or try build from master - it's enough stable for production, and questions may be only for new packages. -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] updating modules.dep
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 box that will be > unavailable w/o ipsec.ko? Reading makefiles is tedious, after all they are meant to be interpreted by machines, not human beings. depmod is done at modules_install in the kernel makefile. The easiest way to regenerate the file is to re-run depmod once the ipsec.ko module is copied to the STAGINg area. Now doing this, the full tree names of the modules are written to the modules.dep file instead of the flat hierarchy used in 4.x. Somewhere this must be stripped. Now what puzzles me is that the build destination for most stuff is not the staging area but the build directory. It appears also that depmod is run against the modules in build and not against the modules in staging. Could someone enlighten me about the reasoning for the two different areas? Thanks Erich smime.p7s Description: S/MIME Kryptografische Unterschrift -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] updating modules.dep
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 11/10/12 17:18, Erich Titl wrote: > 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 modules.dep is not updated. >>> >>> Does anyone know where we run depmod, so it can be called in the >>> openswan build? >>> >> No sure but try to build kmodules > Did already, no luck :-( > > I am looking at .../staging/lib/modules/n.n.n./modules.dep > I used > > /buildtool.pl buildclean kmodules > /buildtool.pl build kmodules > > A... but possibly it is generated when buiding the package > > luna:/home/mega/leaf/devel/leaf.new/bering-uclibc # ./buildpacket.pl > --package=kmodules > Generating package moddb-geode > Generating package moddb-i686 > Generating package moddb-i486 > > But no luck... > > Also the module does not get included in moddb.lrp > > mega@luna:~/leaf/devel/leaf.new/bering-uclibc/package> tar tzf > moddb-i686.lrp | grep ipsec.ko > mega@luna:~/leaf/devel/leaf.new/bering-uclibc/package> > > Neither does it get built at initrd packing > > M... real uncool. > > cheers > > Erich > > -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] updating modules.dep
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 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 build? >>> >> No sure but try to build kmodules > > Did already, no luck :-( > > I am looking at .../staging/lib/modules/n.n.n./modules.dep > I used > > /buildtool.pl buildclean kmodules > /buildtool.pl build kmodules > > A... but possibly it is generated when buiding the package > > luna:/home/mega/leaf/devel/leaf.new/bering-uclibc # ./buildpacket.pl > --package=kmodules > Generating package moddb-geode > Generating package moddb-i686 > Generating package moddb-i486 > > But no luck... > > Also the module does not get included in moddb.lrp > > mega@luna:~/leaf/devel/leaf.new/bering-uclibc/package> tar tzf > moddb-i686.lrp | grep ipsec.ko > mega@luna:~/leaf/devel/leaf.new/bering-uclibc/package> > > Neither does it get built at initrd packing > > M... real uncool. It should be added to the modules tarball when you build an image with buildimage.pl. It's also in staging/lib/modules/2.6.35.14-i686/kernel/net/ipsec kp -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] updating modules.dep
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 modules.dep is not updated. >> >> Does anyone know where we run depmod, so it can be called in the >> openswan build? >> > No sure but try to build kmodules Did already, no luck :-( I am looking at .../staging/lib/modules/n.n.n./modules.dep I used /buildtool.pl buildclean kmodules /buildtool.pl build kmodules A... but possibly it is generated when buiding the package luna:/home/mega/leaf/devel/leaf.new/bering-uclibc # ./buildpacket.pl --package=kmodules Generating package moddb-geode Generating package moddb-i686 Generating package moddb-i486 But no luck... Also the module does not get included in moddb.lrp mega@luna:~/leaf/devel/leaf.new/bering-uclibc/package> tar tzf moddb-i686.lrp | grep ipsec.ko mega@luna:~/leaf/devel/leaf.new/bering-uclibc/package> Neither does it get built at initrd packing M... real uncool. cheers Erich smime.p7s Description: S/MIME Kryptografische Unterschrift -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
Re: [leaf-devel] updating modules.dep
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 run depmod, so it can be called in the > openswan build? > No sure but try to build kmodules Yves -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
[leaf-devel] updating modules.dep
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 build? Thanks Erich smime.p7s Description: S/MIME Kryptografische Unterschrift -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
