From: Sam Ravnborg <sam@ravnborg.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86,build: Fix make -jN modules_install install
Date: Wed, 11 Jun 2014 21:44:52 +0200 [thread overview]
Message-ID: <20140611194452.GA25049@ravnborg.org> (raw)
In-Reply-To: <37910a32e3d223a688a2743376bdde8fbdc8ef5c.1402515662.git.luto@amacapital.net>
On Wed, Jun 11, 2014 at 12:41:57PM -0700, Andy Lutomirski wrote:
> Every few months, I forget why I type:
>
> $ sudo make -j12 modules_install && sudo make -j12 install
>
> instead of just:
>
> $ sudo make -j12 modules_install install
>
> I try the latter, it appears to work, and then my machine won't boot
> because dracut got confused. This fixes it once and for all: if you
> ask make to install modules and a kernel, you almost certainly want
> the modules installed *first* so that your initramfs scripts can
> find the modules.
Is this problem x86 specific?
Sam
next prev parent reply other threads:[~2014-06-11 19:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-11 19:41 [PATCH] x86,build: Fix make -jN modules_install install Andy Lutomirski
2014-06-11 19:44 ` Sam Ravnborg [this message]
2014-06-11 19:46 ` Andy Lutomirski
2014-06-12 8:33 ` Michal Marek
2014-06-13 1:28 ` Andy Lutomirski
2014-06-13 9:39 ` [PATCH] kbuild: Do not run modules_install and install in paralel Michal Marek
2014-06-13 9:45 ` Michal Marek
2014-06-13 17:29 ` Andy Lutomirski
2014-07-04 22:15 ` Michal Marek
2014-07-04 23:45 ` Andy Lutomirski
2014-07-07 11:03 ` Michal Marek
2015-12-09 21:34 ` Andy Lutomirski
2015-12-10 14:45 ` Michal Marek
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=20140611194452.GA25049@ravnborg.org \
--to=sam@ravnborg.org \
--cc=hpa@zytor.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mmarek@suse.cz \
--cc=x86@kernel.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).