mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Russell King <rmk@arm.linux.org.uk>
Cc: vherva@twilight.cs.hut.fi, mikael.starvik@axis.com,
	linux-kernel@vger.kernel.org, tinglett@vnet.ibm.com,
	torvalds@transmeta.com
Subject: Re: zImage now holds vmlinux, System.map and config in sections. (fwd)
Date: Tue, 25 Feb 2003 08:38:11 -0800	[thread overview]
Message-ID: <20030225083811.797fbce6.rddunlap@osdl.org> (raw)
In-Reply-To: <20030225113557.C9257@flint.arm.linux.org.uk>

On Tue, 25 Feb 2003 11:35:57 +0000
Russell King <rmk@arm.linux.org.uk> wrote:

| On Tue, Feb 25, 2003 at 01:07:04PM +0200, Ville Herva wrote:
| > On Tue, Feb 25, 2003 at 09:25:20AM +0000, you [Russell King] wrote:
| > > Agreed - zImage is already around 1MB on many ARM machines, and since
| > > loading zImage over a serial port using xmodem takes long enough
| > > already, this is one silly feature I'll definitely keep out of the
| > > ARM tree.
| > 
| > Why not make it a config option (like the other (two? three?) rejected
| > patches that implemented this did)?
| 
| I, for one, do not see any point in trying to put more and more crap
| into one file, when its perfectly easy to just use the "cp" command
| to produce the same end result, namely a copy of zImage, System.map
| and configuration, thusly:
| 
| cp arch/$ARCH/boot/zImage /boot/vmlinuz-$VERSION
| cp .config /boot/config-$VERSION
| cp System.map /boot/System.map-$VERSION

Yes, that almost matches my 'new.kernel' install script.

| No hastles with configuration options.  No hastles with bloated zImage
| files.  No hastles with adding extra stuff to makefiles to do special
| mangling to zImage.

Yes, you wouldn't have to use it.

| If people are worried about vmlinuz being out of step with config, once
| you add the above to the installation target of the kernel makefile,
| unless you do things manually, you won't get out of step.
| 
| If you're worried about config-* and System.map-* being out of step with
| the kernel you're running, exactly the same applies to the "everything
| in one file" version as well.
| 
| If you need to make a backup of it:
| 
| mkdir /boot/old
| cp /boot/*-$VERSION /boot/old
| 
| Nice.  Simple.  No crap.

I'm just guessing that it will be difficult to convince you otherwise,
but I think you are missing the point of this.  It's not for someone
who already has scripts to handle this or already uses 3+ commands
to handle it every time that they build a new kernel.  It's for
people who are less organized than you are -- gosh, maybe even
for Linux users.

--
~Randy

  parent reply	other threads:[~2003-02-25 16:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-25  6:28 Mikael Starvik
2003-02-25  9:25 ` Russell King
2003-02-25 11:07   ` Ville Herva
2003-02-25 11:35     ` Russell King
2003-02-25 12:03       ` Ville Herva
2003-02-25 14:34         ` Jeremy Jackson
2003-02-26 18:41           ` Peter Bergner
2003-02-25 22:00         ` Bryan Andersen
2003-02-25 12:50       ` Remco Post
2003-02-25 13:35         ` Russell King
2003-02-25 16:38       ` Randy.Dunlap [this message]
2003-02-25 17:52         ` Russell King
2003-02-26 20:01           ` Todd Inglett
2003-02-26 20:45             ` Peter Bergner
2003-02-25 19:22         ` Ville Herva
2003-02-25 16:23   ` Randy.Dunlap
2003-02-25 20:00   ` H. Peter Anvin
2003-02-25 21:24     ` Russell King
2003-02-25 21:52       ` H. Peter Anvin
2003-02-25 23:21 ` Magnus Danielson
     [not found] <Pine.LNX.4.33.0302241010200.1088-100000@localhost.localdomain>
2003-02-24 19:58 ` Randy.Dunlap

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=20030225083811.797fbce6.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikael.starvik@axis.com \
    --cc=rmk@arm.linux.org.uk \
    --cc=tinglett@vnet.ibm.com \
    --cc=torvalds@transmeta.com \
    --cc=vherva@twilight.cs.hut.fi \
    /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

all inboxes | Powered by JetHome®