linux-kernel - Re: x86: removing zImage support?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.2.00.0903111201430.29264@localhost.localdomain>
Date:	Wed, 11 Mar 2009 12:03:24 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Ingo Molnar <mingo@...e.hu>
cc:	"H. Peter Anvin" <hpa@...or.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	the arch/x86 maintainers <x86@...nel.org>
Subject: Re: x86: removing zImage support?

On Wed, 11 Mar 2009, Ingo Molnar wrote:
> * H. Peter Anvin <hpa@...or.com> wrote:
> 
> > I'm thinking again about removing zImage support.  An 
> > "allnoconfig" kernel (with CONFIG_EMBEDDED=y to expose 
> > additional knobs, and CONFIG_BINFMT_ELF=y so it can do 
> > anything at all) is currently 487K on i386 -- very close to 
> > the upper limit of 512K for zImage.
> > 
> > Are there *any* residual users of this, or should I just push 
> > a patch to remove it once and for all?
> 
> Havent seen any zImage bugreport for years, so go for it. In the 
> unlikely case of someone still relying on it and having a good 
> use case we'll get a bugreport and can consider putting it back 
> in.

I haven't seen any zImage for years in the embedded space either.
Go for it.

Thanks,

	tglx


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/