Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: kmod packaging question
Date: Tue, 15 Oct 2013 21:44:13 -0600	[thread overview]
Message-ID: <525E0B8D.8070008@mlbassoc.com> (raw)
In-Reply-To: <525DDC90.4050700@linux.intel.com>

On 2013-10-15 18:23, Saul Wold wrote:
> On 10/15/2013 05:17 PM, Saul Wold wrote:
>> On 10/14/2013 10:00 AM, Gary Thomas wrote:
>>> I'm having some issues with the 'kmod' package.  In particular,
>>> the package claims:
>>>    commit b4bc0a7f1b90a51e26d6ab74d964ff81cfe05904
>>>    Author: Khem Raj <raj.khem@gmail.com>
>>>    Date:   Tue Jan 31 00:34:01 2012 -0800
>>>
>>>      kmod: Add recipes
>>>
>>>      kmod is replacement for module-init-tools
>>>
>>>      (From OE-Core rev: 716606f5446534e48b45fcc017e8bbdfe7f15e26)
>>>
>>>      Signed-off-by: Khem Raj <raj.khem@gmail.com>
>>>      Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>>>
>>> But is is really a "replacement"?  I know that there is a provides
>>> which makes the build happy, but unless you explicitly install the
>>> kmod package into your image, you don't end up with all of the module
>>> tools.  The main missing piece is 'depmod' - the rest seem to come
>>> from busybox, not kmod.
>>>
>>> I ran into this when trying to run 'opkg upgrade' which sucked in
>>> some new kernel modules and found that 'depmod' was not installed.
>>>
>>> Did I miss something?
>>>
>> Nope, it was a good catch, I will investigate the size increase for
>> adding depmod into busybox.
>>
> Seems it adds 2240 bytes to the size of the busybox binary, that's far better than 675K that kmod would bring in.  I will get the patch up shortly.

Cool, thanks!!

>>> n.b. this was tested using Poky/Yocto
>>> 0fc8317c6385eb1ed69ca4522ee6424c456dbb92
>>> which is a few days old.  I've not checked the very latest master (yet).
>>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
>>

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


      reply	other threads:[~2013-10-16  3:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-14 17:00 kmod packaging question Gary Thomas
2013-10-16  0:17 ` Saul Wold
2013-10-16  0:23   ` Saul Wold
2013-10-16  3:44     ` Gary Thomas [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=525E0B8D.8070008@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox