From: Michal Marek <mmarek@suse.cz>
To: Richard Weinberger <richard@nod.at>, mike.marciniszyn@intel.com
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
OpenSUSE Kernel Team <opensuse-kernel@opensuse.org>
Subject: Re: Kernel binrpm produces brokes grub2 config
Date: Tue, 29 Jul 2014 14:23:54 +0200 [thread overview]
Message-ID: <53D7925A.8080200@suse.cz> (raw)
In-Reply-To: <53D774F9.3090305@nod.at>
On 2014-07-29 12:18, Richard Weinberger wrote:
> Hi!
>
> I'm not sure who to blame, but the below commit breaks the kernel binrpm target for me.
> It produces a faulty grub2 config.
> After installing such a kernel grub2 looks for vmlinuz-XY-rpm and initrd-XY-rpm.
> These files are not existing and the machine does no longer boot.
> Luckily an addition boot entry without the -rpm suffix exists, if remote access works
> one can recover the machine.
>
> My question is, why do we need these copy of vmlinuz anyway?
> After calling installkernel on the -rpm variants you delete them again...
The typical /sbin/installkernel script does a cp "$2" "/boot/...", so
you can't use the already installed files as its arguments.
> This <insert swear word here> happens on openSUSE 13.1, maybe their installkernel script needs fixing.
I guess that the problem is that grub2-mkconfig sees the temporary
/boot/vmlinuz-*-rpm file and creates a menu entry for it. I guess we
should create the temporary kernel and initrd files somewhere else than
in /boot.
Michal
next prev parent reply other threads:[~2014-07-29 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 10:18 Kernel binrpm produces brokes grub2 config Richard Weinberger
2014-07-29 12:23 ` Michal Marek [this message]
2014-07-29 15:22 ` [opensuse-kernel] " Andrey Borzenkov
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=53D7925A.8080200@suse.cz \
--to=mmarek@suse.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.marciniszyn@intel.com \
--cc=opensuse-kernel@opensuse.org \
--cc=richard@nod.at \
/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