From: Jan Kiszka <jan.kiszka@siemens.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] meta: Run depmod after kernel module installation
Date: Mon, 9 Jul 2018 10:05:25 +0200 [thread overview]
Message-ID: <28e2c43a-adea-4d09-3a32-e9529e6e073a@siemens.com> (raw)
In-Reply-To: <20180709094821.0ebc78d5@md1pvb1c.ad001.siemens.net>
On 2018-07-09 09:48, Henning Schild wrote:
> Am Mon, 9 Jul 2018 08:31:12 +0200
> schrieb "[ext] Jan Kiszka" <jan.kiszka@siemens.com>:
>
>> Otherwise the module may not be found if the module package is
>> installed on its own, i.e. without the kernel package performing the
>> depmod run.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>> ---
>> meta/recipes-kernel/linux-module/files/debian/postinst | 4 ++++
>> 1 file changed, 4 insertions(+)
>> create mode 100644
>> meta/recipes-kernel/linux-module/files/debian/postinst
>>
>> diff --git a/meta/recipes-kernel/linux-module/files/debian/postinst
>> b/meta/recipes-kernel/linux-module/files/debian/postinst new file
>> mode 100644 index 0000000..baabf5d
>> --- /dev/null
>> +++ b/meta/recipes-kernel/linux-module/files/debian/postinst
>> @@ -0,0 +1,4 @@
>> +#!/bin/sh
>> +set -e
>> +
>> +depmod -a
>
> That being 644 and the chmod in comnbination with AUTOLOAD do not seem
> to match. Either debian will take care of +x and the chmod is not
> required at all, or it needs to be 755 and the chmod needs to go away.
>
Right, it's probably needed. At least all non-dpkg-raw hooks I found
have +x, and dpkg-raw does an install -m 755.
Jan
prev parent reply other threads:[~2018-07-09 8:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 6:31 Jan Kiszka
2018-07-09 7:48 ` Henning Schild
2018-07-09 8:05 ` Jan Kiszka [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=28e2c43a-adea-4d09-3a32-e9529e6e073a@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.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