In the documentation "Bering-uClibc Developer Guide" -> "Chapter 3. Creating lrp packages with buildpacket" say:
Since it is not obvious at first, a little clarification: buildpacket creates lrp packages (packagename.lrp) that are defined in buildtool setups (unfortunately, those are sometimes also called packages). Those two need not have the same name. The package moddb.lrp does not fulfill the last rule. Is it an exception? How can I create the package configdb.lrp? On 1/10/07, Eric Spakman <[EMAIL PROTECTED]> wrote: > Hi Alejandro, > > > If I use the image Bering-uClibc_3.0-beta3_img_bering-uclibc-1680.bin > > and run it, I can see this: > > > > firewall# ls /lib/modules 2.4.33 > > 8139too.o > > 8390.o > > crc32.o ... > > > > but in my compilation > > > > firewall#ls /lib/modules 2.4.33 > > > > Where is the other modules? > > > > If I write: ./buildtool.pl describe|grep moddb > > > > > > I do not see this package :( > > > You have to copy the moddb.lrp package to the image. It's created with: > ./buildtool.pl build kmodules > ./buildpacket.pl --package=kmodules > > > Eric > > > > > > On 1/10/07, Eric Spakman <[EMAIL PROTECTED]> wrote: > > > >> Hi Alejandro, > >> > >> > >>> Hola, I am compiling everything from zero using the tools buildtool > >>> and ultimately to create the image I use createimage.sh but it don't > >>> add the modules of the kernel *.o to the image. > >>> > >>> I have seen in the CVS that the last modification on this script > >>> tell: > >>> > >>> > >>> > >>> Log Message: > >>> remove the modules tree and link the modules isntead to modules.tgz so > >>> we can use Paul S. Traina's build-modules script > >>> > >>> Where this script is to copy the necessary modules in the > >>> modules.lpr? > >>> > >> The script is called "build-modules", but it's meant to be run from the > >> Bering-uClibc system itself to copy modules listed in /etc/modules > >> from the modules tarball to the moddb. The most common use for it is on > >> an ISO or HD. > >> > >> If you want to create an image yourself with the use of buildtool, you > >> can just use the standard created moddb.lrp package as a starting point. > >> > >> > >> If you want to create your own version of moddb.lrp, with specific > >> modules, you can edit buildtool/kmodules/buildtool.cfg and define the > >> modules you want to include in the moddb. After "./buildtool.pl build > >> kmodules" and "./buildpacket.pl --package=kmodules" you will have your > >> own moddb.lrp package. > >> > >>> > >>> Bye. > >>> > >>> > >>> > >> Eric > >> > >> > >> > >> > > > > > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ------------------------------------------------------------------------ leaf-user mailing list: [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
