From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] What's up with the kernel names? (Again)
Date: Thu, 12 Feb 2009 19:16:25 +0100 [thread overview]
Message-ID: <DC9C4AC978BF4D23BD014FFB5ACEA3FF@aeglos> (raw)
In-Reply-To: 87zlgsg26x.fsf@macbook.be.48ers.dk
>
> Hi,
>
> Ulf> Just for fun, I checked my OpenSuSE /boot directory
>
> Ulf> Guess what I found:
>
> Ulf> "vmlinuz" which happens to be a LINK to
>
> Ulf> ??vmlinuz-$(KERNEL_VERSION)-$(REV)-$PROJECT)
> Ulf> ?
> Ulf> There was also a:
> Ulf> vmlinux-$(KERNEL_VERSION)-$(REV)-$PROJECT).gz file
>
> Ulf> Looks like the guys doing OpenSuSE are as "odd" as I am.
>
> And guess what the kernel outputs? A simple arch/x86/boot/bzImage, as
> platform/distribution specific naming convention doesn't belong in the
> mainline kernel.
>
No but it belongs in the distribution created by buildroot.
Try making a remote upgrade when the old kernel and the new kernel has the
same name.
Your argument smells of
"we have always done it in a certain way, and therefore we should always do
it in the same way".
There are some reasons why you may want to have a simple name,
and all these reasons are covered by generating a symlink.
It is a good idea to make things as simple as possible, you are trying to
make things simpler than that.
Best Regards
Ulf Samuelsson
next prev parent reply other threads:[~2009-02-12 18:16 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 1:49 [Buildroot] What's up with the kernel names? (Again) Thiago A. Corrêa
2009-02-04 7:39 ` Peter Korsgaard
2009-02-04 12:29 ` Peter Korsgaard
2009-02-05 2:33 ` Thiago A. Corrêa
2009-02-05 13:23 ` Peter Korsgaard
2009-02-05 20:37 ` Ulf Samuelsson
2009-02-06 2:28 ` Thiago A. Corrêa
2009-02-06 6:16 ` Ulf Samuelsson
2009-02-06 8:49 ` Peter Korsgaard
2009-02-06 9:06 ` Ulf Samuelsson
2009-02-06 12:30 ` Peter Korsgaard
2009-02-06 8:45 ` Peter Korsgaard
2009-02-06 8:58 ` Ulf Samuelsson
2009-02-06 8:44 ` Peter Korsgaard
2009-02-05 20:23 ` Ulf Samuelsson
2009-02-06 8:41 ` Peter Korsgaard
2009-02-06 8:56 ` Ulf Samuelsson
2009-02-06 12:27 ` Peter Korsgaard
2009-02-06 14:31 ` Thiago A. Corrêa
2009-02-06 15:18 ` Thiago A. Corrêa
2009-02-09 17:24 ` Ulf Samuelsson
2009-02-09 19:34 ` Peter Korsgaard
2009-02-09 22:52 ` Ulf Samuelsson
2009-02-10 1:25 ` Thiago A. Corrêa
2009-02-10 8:02 ` Ulf Samuelsson
2009-02-10 9:28 ` Peter Korsgaard
2009-02-10 10:32 ` Ulf Samuelsson
2009-02-10 9:17 ` Peter Korsgaard
2009-02-10 10:16 ` Ulf Samuelsson
2009-02-10 12:51 ` Peter Korsgaard
2009-02-10 13:50 ` Ulf Samuelsson
2009-02-10 16:34 ` Thiago A. Corrêa
2009-02-10 17:17 ` Thiago A. Corrêa
2009-02-10 17:42 ` Ulf Samuelsson
2009-02-10 18:48 ` Thiago A. Corrêa
2009-02-11 20:03 ` Ulf Samuelsson
2009-02-11 20:15 ` Peter Korsgaard
2009-02-12 18:16 ` Ulf Samuelsson [this message]
2009-02-16 22:21 ` Thiago A. Corrêa
2009-02-17 11:26 ` Peter Korsgaard
2009-02-10 18:26 ` Ulf Samuelsson
2009-02-10 18:50 ` Ulf Samuelsson
2009-02-10 20:06 ` Thiago A. Corrêa
2009-02-10 18:59 ` Ulf Samuelsson
2009-02-10 19:49 ` Ulf Samuelsson
2009-02-10 20:06 ` Peter Korsgaard
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=DC9C4AC978BF4D23BD014FFB5ACEA3FF@aeglos \
--to=ulf.samuelsson@atmel.com \
--cc=buildroot@busybox.net \
/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