From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?ISO-8859-1?Q?Thiago_A._Corr=EAa?= <thiago.correa@gmail.com>
Date: Mon, 7 Jan 2008 14:41:42 -0200
Subject: [Buildroot] [PATCH] Create /boot/uImage symlink to the
	currentkernel image
In-Reply-To: <028e01c85141$ba1d0fd0$030514ac@atmel.com>
References: <d6cda7730801031650i439f5821h566eeef460615172@mail.gmail.com>
	<028e01c85141$ba1d0fd0$030514ac@atmel.com>
Message-ID: <d6cda7730801070841l4a5b1f6ahcbdbcb0bbbef2b87@mail.gmail.com>
List-Id: <buildroot.busybox.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: buildroot@busybox.net

On Jan 4, 2008 11:45 AM, Ulf Samuelsson <ulf@atmel.com> wrote:
>
>
>
> | Hi,
> |
> |   A while ago, the kernel naming have been changed to include $(DATE)
> | which makes it annoying to keep track. This patch adds an option to
> | the Advanced Kernel option to create an /boot/uImage symbolic link to
> | the built kernel. Please consider applying, this really improves
> | usability, if this naming scheme is to be kept.
> |
> | Kind Regards,
> |    Thiago A. Correa
> |
>
> Looking at your patch, I see that we are talking about two different things.
> There is a feature to copy the linux kernel to /tftpboot directory,
> which I thought you were referring to, but If you want the kernel inside
> the root file system, then would it not make more sense to do:
>
> -  cp -dpf $(LINUX26_KERNEL) $(TARGET_DIR)/boot/$(LINUX26_KERNEL_NAME)
> +  cp -dpf $(LINUX26_KERNEL) $(TARGET_DIR)/boot/$(BR2_PACKAGE_LINUX_FORMAT)
>
> where BR2_PACKAGE_LINUX_FORMAT could be
> uImage, bzImage, vmlinux etc.
>
> Best Regards
> Ulf Samuelsson
>

Yes, that was the previous behavior, although perhaps not exactly the
same code, I haven't checked the svn logs to see how it was before.
Anyway, since I'm not sure why it changed in the first place, I
suggested the symlinking as an option.

Regards,
   Thiago A. Correa