mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Colin Guthrie <gmane-D409yXkIzt2rnn0nCzrM/w@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] Use modinfo to gather module dependencies
Date: Mon, 27 Feb 2012 13:08:23 +0100	[thread overview]
Message-ID: <4F4B7237.6070005@redhat.com> (raw)
In-Reply-To: <jifpfl$hof$1@dough.gmane.org>

Am 27.02.2012 12:29, schrieb Colin Guthrie:
> 'Twas brillig, and Harald Hoyer at 27/02/12 10:25 did gyre and gimble:
>> Am 25.02.2012 22:09, schrieb Dennis Schridde:
>>> Hello!
>>
>>> I just switched from module-init-tools to kmod and found dracut broken, 
>>> because it uses modprobe --show-depends to find out about module locations
>>> and dependencies, which apparently is not implemented in kmod.
>>
>>> Hence I wrote attached patch, switching from modprobe to modinfo, which
>>> also seem to be the tool intended for the job. This method appears to work
>>> reliable in kmod-5, but I have not tested with module-init-tools.
>>
>>> Kind regards, Dennis
>>
>> You need this patch for kmod:
>>
>> http://git.profusion.mobi/cgit.cgi/kmod.git/commit/?id=269de2e0bf5011072da2f40f4f2d4023fad696b9
> 
> What does this patch add?
> 
> I seem to get modprobe working happily with kmod 5 even for non-loaded
> modules. With patch applied or not, the output was the same.
> 
> I'd just like to understand the issue :)

Have you replaced module-init-tools with kmod? If not, then this problem does
not affect you.

  reply	other threads:[~2012-02-27 12:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-25 21:09 [PATCH] Use modinfo to gather module dependencies Dennis Schridde
2012-02-27 10:25 ` Harald Hoyer
     [not found]   ` <4F4B5A00.2060400-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-02-27 11:29     ` Colin Guthrie
2012-02-27 12:08       ` Harald Hoyer [this message]
     [not found]         ` <4F4B7237.6070005-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-02-27 12:33           ` Colin Guthrie
     [not found] ` <CALAkbJMqL-p95Yb=jsP8BZAjhJkByHn-QZV=C0nmsTkMW1qZ1Q@mail.gmail.com>
     [not found]   ` <CALAkbJMqL-p95Yb=jsP8BZAjhJkByHn-QZV=C0nmsTkMW1qZ1Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-02-27 12:39     ` Dennis Schridde

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=4F4B7237.6070005@redhat.com \
    --to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=gmane-D409yXkIzt2rnn0nCzrM/w@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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