mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Christian Heinz
	<christian.ch.heinz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] fix installation of `modules.builtin.bin'
Date: Fri, 26 Nov 2010 09:36:42 +0100	[thread overview]
Message-ID: <4CEF719A.6060209@redhat.com> (raw)
In-Reply-To: <1290738077-17335-1-git-send-email-christian.ch.heinz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

Am 26.11.2010 03:21, schrieb Christian Heinz:
> `modules.builtin.bin' is installed like a regular file, thereby ending
> up in the wrong place when `--kmoddir' is in effect. Fix this by
> specifying the installation destination.
> ---
>   modules.d/90kernel-modules/install |    2 +-
>   1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/modules.d/90kernel-modules/install b/modules.d/90kernel-modules/install
> index 863ffac..b635216 100755
> --- a/modules.d/90kernel-modules/install
> +++ b/modules.d/90kernel-modules/install
> @@ -4,4 +4,4 @@
>   [ -f /etc/modprobe.conf ]&&  dracut_install /etc/modprobe.conf
>   dracut_install $(find /etc/modprobe.d/ -type f -name '*.conf')
>   inst_hook cmdline 01 "$moddir/parse-kernel.sh"
> -inst "$srcmods/modules.builtin.bin"
> +inst "$srcmods/modules.builtin.bin" "/lib/modules/$kernel/modules.builtin.bin"


pushed

      parent reply	other threads:[~2010-11-26  8:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-26  2:21 [PATCH] fix installation of `modules.builtin.bin' Christian Heinz
     [not found] ` <1290738077-17335-1-git-send-email-christian.ch.heinz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-11-26  8:36   ` Harald Hoyer [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=4CEF719A.6060209@redhat.com \
    --to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=christian.ch.heinz-Re5JQEeQqe8AvxtiuMwx3w@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