Github messages for voidlinux
 help / color / mirror / Atom feed
From: MaMiMa81 <MaMiMa81@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: "depmod: WARNING" after kmod update
Date: Fri, 12 Aug 2022 15:29:42 +0200	[thread overview]
Message-ID: <20220812132942.dhhCPzs_SFLUd4EcDDtyIoKzNkSW4DrFIUrkVI6Fjes@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38367@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1639 bytes --]

New comment by MaMiMa81 on void-packages repository

https://github.com/void-linux/void-packages/issues/38367#issuecomment-1213111549

Comment:
> Latest dracut v.056 seems to have this covered, not tested though:
> 
> dracut-init.sh line 1001:
> 
> `dracut_kernel_post() { for _f in modules.builtin modules.builtin.alias modules.builtin.modinfo modules.order; do [[ -e $srcmods/$_f ]] && inst_simple "$srcmods/$_f" "/lib/modules/$kernel/$_f" done`

Good Afternoon
regarding this issue and taking into account what has been mentioned by @ahesford that a full update of dracut to v.56 will require extensive testing - espescially as it appears that it is moving to be more systemd centric - plus this will also alleviate demand upon core devs, would not a simple & sensible course
of action just be to administer a basic patch to the existing dracut v.53:

        985  - for _f in modules.builtin.bin modules.builtin modules.order; do

        985  + for _f in modules.builtin.bin modules.builtin modules.builtin.modinfo modules.order; do

I wouldn't know how to set this up correctly in a patch & submit it for inclusion as a new 'revision'??? - I could hazard a guess by looking around but that's just what it would be. I am no programmer & this is purely a effort to perhaps solve this in the easiest manner. As, how shall we say a 'lay-person', I shouldn't of thought this wouldn't have too much, if any, ramifications on things - but again quite frankly that is pretty much a guess, the much more knowledgable amongst you here will have more of an idea - I merely but it forward as a suggestion to try and help.
Regards

  parent reply	other threads:[~2022-08-12 13:29 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-30 10:20 [ISSUE] " Haagen-Dazs
2022-07-30 13:36 ` Haagen-Dazs
2022-08-05 17:52 ` TeusLollo
2022-08-05 17:54 ` TeusLollo
2022-08-05 17:54 ` TeusLollo
2022-08-05 17:54 ` TeusLollo
2022-08-07  2:13 ` Haagen-Dazs
2022-08-07 17:52 ` TeusLollo
2022-08-07 17:52 ` TeusLollo
2022-08-07 17:58 ` TeusLollo
2022-08-07 20:51 ` Haagen-Dazs
2022-08-08  1:34 ` ahesford
2022-08-08  9:12 ` TeusLollo
2022-08-12 13:29 ` MaMiMa81 [this message]
2022-08-12 13:30 ` MaMiMa81
2022-08-12 13:34 ` MaMiMa81
2022-08-12 14:45 ` MaMiMa81
2022-08-12 14:56 ` MaMiMa81
2022-08-12 16:24 ` TeusLollo
2022-08-17 17:13 ` MaMiMa81
2022-08-17 17:15 ` MaMiMa81
2022-08-17 17:23 ` MaMiMa81
2022-08-17 17:25 ` MaMiMa81
2022-08-17 17:26 ` MaMiMa81
2022-08-17 17:29 ` ahesford
2022-08-17 19:59 ` TeusLollo
2022-08-17 20:00 ` TeusLollo
2022-08-18 15:12 ` MaMiMa81
2022-08-22 15:22 ` TeusLollo
2022-08-23 15:49 ` [ISSUE] [CLOSED] " ahesford

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=20220812132942.dhhCPzs_SFLUd4EcDDtyIoKzNkSW4DrFIUrkVI6Fjes@z \
    --to=mamima81@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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;
as well as URLs for NNTP newsgroup(s).