[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071005053813.GA25242@elte.hu>
Date: Fri, 5 Oct 2007 07:38:13 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Alistair John Strachan <alistair@...zero.co.uk>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Andi Kleen <ak@...e.de>, Thomas Gleixner <tglx@...utronix.de>,
Sam Ravnborg <sam@...nborg.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Linux 2.6.23-rc9 and a heads-up for the 2.6.24 series..
* Alistair John Strachan <alistair@...zero.co.uk> wrote:
> On Tuesday 02 October 2007 04:41:49 Linus Torvalds wrote:
> [snip]
> > In other words, people who know they may be affected and would want to
> > prepare can look at (for example)
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tglx/linux-2.6-x86.git x86
> >
> > and generally get ready for the switch-over.
>
> This is certainly a tool issue, but if I use Debian's kernel-image "make-kpkg"
> wrapper around the kernel build system, it fails with:
>
> cp: cannot stat `arch/x86_64/boot/bzImage': No such file or directory
>
> Obviously, this file has moved to arch/x86/boot, but it seems like
> possibly unnecessary breakage. I've been copying bzImage for years
> from arch/x86_64/boot, and I'm sure there's a handful of scripts
> (other than Debian's kernel-image) doing this too.
>
> For now, I hacked the tool[1]. Maybe, if we care, a symlink could be
> set up between arch/x86/boot and arch/$ARCH/boot ? Or would papering
> over this be more trouble than it's worth?
yeah, a symlink is the right solution i think. Our first-step goal is to
make the switchover seamless for all practical purposes, and a
compatibility symlink in arch/i386/boot/ will not hurt. (we shouldnt
worry about the really old zImage target though)
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists