From: Zdenek Kaspar <zkaspar82@gmail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: make tar*-pkg considered dangerous
Date: Wed, 12 Sep 2012 18:43:45 +0200 [thread overview]
Message-ID: <5050BBC1.1090207@gmail.com> (raw)
In-Reply-To: <20120912031646.GV16230@one.firstfloor.org>
On 09/12/2012 05:16 AM, Andi Kleen wrote:
>
> Hi,
>
> We've had some incidents with people destroying Fedore 17 installs
> (to the point of reinstall) by installing a kernel tarball generated with
> make tar*-pkg
>
> The problem is that the tarball includes /lib/{modules,firmware},
> but on FC17 /lib is a symlink. tar when it unpacks the tarball
> replaces the symlink with the directory. So they end up
> with a /lib which only contains the new kernel files, but nothing else,
>
> And then the system doesn't boot anymore.
>
> I'm not sure there is a good fix for this. I don't know of a way to
> convince tar to not do that. And putting everything into /usr
> would be very incompatible.
>
> Disable these make targets or add warnings? If disabling people should
> use rpms or dpkgs instead?
>
> -Andi
>
I dont use the dpkg/rpm variants myself, but unpack with -h should be
enough?
HTH, Z.
next prev parent reply other threads:[~2012-09-12 16:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 3:16 make tar*-pkg considered dangerous Andi Kleen
2012-09-12 16:43 ` Zdenek Kaspar [this message]
[not found] ` <20120912161154.GB3289@khazad-dum.debian.net>
2012-09-12 20:39 ` (fwd) " Ben Hutchings
2012-09-19 11:58 ` Thorsten Glaser
2012-09-25 22:17 ` [PATCH] kbuild: Do not package /boot and /lib in make tar-pkg Michal Marek
2012-09-26 16:08 ` Andi Kleen
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=5050BBC1.1090207@gmail.com \
--to=zkaspar82@gmail.com \
--cc=andi@firstfloor.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.