All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alistair John Strachan <alistair@devzero.co.uk>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Sam Ravnborg <sam@ravnborg.org>, Ingo Molnar <mingo@elte.hu>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andi Kleen <ak@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Linux 2.6.23-rc9 and a heads-up for the 2.6.24 series..
Date: Mon, 8 Oct 2007 00:44:49 +0100	[thread overview]
Message-ID: <200710080044.49883.alistair@devzero.co.uk> (raw)
In-Reply-To: <alpine.LRH.0.999.0710051026200.10191@www.tglx.de>

On Friday 05 October 2007 09:32:40 you wrote:
> On Fri, 5 Oct 2007, Sam Ravnborg wrote:
> > > > 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)
> >
> > But when can we then get rid of it?
> > This is a simple question about when we take the noise..
> > And right now people know we are shifting to x86 - so it makes
> > sense to let the dependent userspace tools take the pain now and not
> > later.
> >
> > Starting to fill up a build kernel with symlinks for compatibility with
> > random progarms seems to be the wrong approach.
> >
> > 	Sam - that dislike especially the asm symlink
>
> Sam,
>
> I completely agree with you, but we want to keep the migration noise
> as low as possible. Adding the symlink right now along with an entry
> into features-removal.txt (6 month grace period) allows a smoother
> transition. The distro folks should better get their gear together
> until then.

I'll certainly file a bug report with the Debian BTS, but the fix will 
probably involve something as abortive as my original patch.

How did the PPC merge handle this? I can't see any similar hacks in 
kernel-image for these architectures.

-- 
Cheers,
Alistair.

137/1 Warrender Park Road, Edinburgh, UK.

  reply	other threads:[~2007-10-07 23:44 UTC|newest]

Thread overview: 85+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.LFD.0.999.0710012029400.3579@woody.linux-foundation.org >
2007-10-02  3:41 ` Linux 2.6.23-rc9 and a heads-up for the 2.6.24 series Linus Torvalds
2007-10-02  9:17   ` Thomas Gleixner
2007-10-02  9:21     ` Andi Kleen
2007-10-02 10:37       ` Jeff Garzik
2007-10-02 10:48         ` Andi Kleen
2007-10-02 11:05           ` Thomas Gleixner
2007-10-02 14:07             ` Ingo Molnar
2007-10-02 14:23               ` Andi Kleen
2007-10-02 14:31                 ` Ingo Molnar
2007-10-02 14:54                   ` Andi Kleen
2007-10-02 14:58                   ` Sam Ravnborg
2007-10-02 15:24                     ` Andi Kleen
2007-10-02 15:27                     ` Ingo Molnar
2007-10-02 15:30                     ` Thomas Gleixner
2007-10-02 15:40                       ` Sam Ravnborg
2007-10-02 12:04       ` Jiri Kosina
2007-10-02 20:12     ` Rafael J. Wysocki
2007-10-02 20:11       ` Andrew Morton
2007-10-02 20:31         ` Rafael J. Wysocki
2007-10-02 20:32         ` Roland Dreier
2007-10-03  3:53     ` Eric St-Laurent
2007-10-02 12:07   ` Mel Gorman
2007-10-02 12:15     ` Ingo Molnar
2007-10-02 17:21       ` Mel Gorman
2007-10-02 22:09         ` Bill Davidsen
2007-10-03  0:37           ` Mel Gorman
2007-10-03  8:21             ` Ingo Molnar
2007-10-03 12:51               ` Mel Gorman
2007-10-22 15:56                 ` Ingo Molnar
2007-10-03  8:19         ` Ingo Molnar
2007-10-02 14:44   ` John Stoffel
2007-10-02 15:03     ` Ingo Molnar
2007-10-02 15:45     ` John Stoffel
2007-10-02 22:13     ` Bill Davidsen
2007-10-02 22:44   ` Willy Tarreau
2007-10-02 22:51   ` Alistair John Strachan
2007-10-02 23:00     ` Glauber de Oliveira Costa
2007-10-05  5:41       ` Ingo Molnar
2007-10-05  5:38     ` Ingo Molnar
2007-10-05  6:11       ` Sam Ravnborg
2007-10-05  8:32         ` Thomas Gleixner
2007-10-07 23:44           ` Alistair John Strachan [this message]
2007-10-02 23:07   ` Diego Calleja
2007-10-02 23:32     ` Linus Torvalds
2007-10-03 15:28       ` Diego Calleja
2007-10-03  8:46   ` [bug] crash when reading /proc/mounts (was: Re: Linux 2.6.23-rc9 and a heads-up for the 2.6.24 series..) Ingo Molnar
2007-10-03  8:50     ` Ingo Molnar
2007-10-03  9:12       ` Ingo Molnar
2007-10-03  9:23         ` Ingo Molnar
2007-10-03 13:34     ` Al Viro
2007-10-03 14:08       ` Ingo Molnar
2007-10-03 14:26         ` Al Viro
2007-10-03 15:12           ` Arjan van de Ven
2007-10-03 15:11     ` Linus Torvalds
2007-10-03 15:40       ` Ingo Molnar
2007-10-03 16:07         ` Linus Torvalds
2007-10-03 15:47       ` Linus Torvalds
2007-10-03 15:49         ` Ingo Molnar
2007-10-03 16:07           ` Ingo Molnar
2007-10-03 15:51       ` Alan Cox
2007-10-03 16:09         ` Linus Torvalds
2007-10-03 16:25           ` Jan Engelhardt
2007-10-03 17:07             ` Linus Torvalds
2007-10-04 14:12       ` Adrian Bunk
2007-10-04 15:08         ` Alexey Dobriyan
2007-10-03 14:21   ` Linux 2.6.23-rc9 and a heads-up for the 2.6.24 series Timo Jantunen
2007-10-03 19:07   ` Jeff Garzik
2007-10-03 19:25     ` Linus Torvalds
2007-10-04 11:55   ` [patch] net, 9p: build fix with !CONFIG_SYSCTL Ingo Molnar
2007-10-04 17:05   ` [BUG] Linux 2.6.23-rc9 and MAX_ARG_PAGES Mathieu Chouquet-Stringer
2007-10-04 17:17     ` Peter Zijlstra
2007-10-04 20:47       ` Mathieu Chouquet-Stringer
2007-10-04 21:58       ` Mathieu Chouquet-Stringer
2007-10-04 17:27     ` Linus Torvalds
2007-10-04 20:44       ` Mathieu Chouquet-Stringer
2007-10-04 21:21         ` Linus Torvalds
2007-10-04 22:27           ` Paul Mackerras
2007-10-05  0:12             ` Linus Torvalds
2007-10-05  3:22               ` Mathieu Chouquet-Stringer
2007-10-05  7:43                 ` Peter Zijlstra
2007-10-04 21:50     ` Chuck Ebbert
2007-10-04 21:54       ` Mathieu Chouquet-Stringer
2007-10-06  8:29     ` Hans-Peter Jansen
2007-10-06 11:29       ` Hans-Peter Jansen
2007-10-06 17:36     ` Bill Davidsen

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=200710080044.49883.alistair@devzero.co.uk \
    --to=alistair@devzero.co.uk \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sam@ravnborg.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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.