Re: zImage now holds vmlinux, System.map and config in sections. (fwd)

[Peter Bergner <bergner@vnet.ibm.com>]

Jeremy Jackson wrote:
 > From a pure technical point of view, it seems just like bloat.  But from a
 > distribution, maintenance, etc point of view, it's a godsend.  It's a config
 > option, just like devfs and initrd, so just don't use it if you don't want
 > to.

It was precisely for those reasons I made the changes (Todd Inglett was nice
enough to push the changes for me, hence his name on the change set).  The PPC64
arch is a server platform, so the extra disk space caused by the bloat in the
zImage isn't a problem.  However, the benefits of having the attached sections
is a godsend when a customer calls you up with a kernel problem and all they
can give you (they may not be very adept with Linux) is the zImage and some
type of error message.


Russell King wrote:
 > So you want to transfer the complete zImage, including the redundant
 > configuration and system.map to the target over the network, only to
 > have it thrown away?

For our architecture, why not?  We're not short on disk space and we can
netboot, so no problems there.  Yeah, for ARM and other embedded arches,
it may not be what you want to do, but for PPC64, it's a good solution.



Peter