Re: zImage now holds vmlinux, System.map and config in sections. (fwd)
H. Peter Anvin (email@example.com)
25 Feb 2003 12:00:14 -0800
Followup to: <20030225092520.A9257@flint.arm.linux.org.uk>
By author: Russell King <firstname.lastname@example.org>
In newsgroup: linux.dev.kernel
> On Tue, Feb 25, 2003 at 07:28:46AM +0100, Mikael Starvik wrote:
> > >I don't know linker scripts very well.
> > >Can this be done for all architectures?
> > >I'd like to see a solution that is arch-independent.
> > In embedded systems it is probably not desirable to keep
> > System.map and config in zImage (takes too much valuable space).
> 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.
Isn't that what "strip" is for?
<email@example.com> at work, <firstname.lastname@example.org> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: cris ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/