linux-kernel - Re: x86 (Linux Tiny): configure out support for some processors

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20090102162357.GH1180@elte.hu>
Date:	Fri, 2 Jan 2009 17:23:57 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Valdis.Kletnieks@...edu
Cc:	Jaswinder Singh Rajput <jaswinderlinux@...il.com>,
	Bryan Donlan <bdonlan@...il.com>,
	Ingo Brueckl <ib@...peronline.de>,
	linux-kernel@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: x86 (Linux Tiny): configure out support for some processors


* Valdis.Kletnieks@...edu <Valdis.Kletnieks@...edu> wrote:

> On Fri, 02 Jan 2009 21:43:03 +0530, Jaswinder Singh Rajput said:
> 
> > Let me know why should I choose EMBEDDED option ? I know I am not 
> > using Embbeded machine and I do not need embbeded features on my 
> > machine. If I am willing to go North why should I go South first ?
> 
> EMBEDDED is a bad name for the option.  It *started* as "only those 
> maniac who need to trim their kernel WAY down should select this", and 
> ended up as "stuff that 95% of users shouldn't change, but you can if 
> you know what you're doing".

i think both activities fit the generic 'embedded/specialized kernel' term 
quite well, so i dont think there's a big naming problem. There's maybe a 
documentation problem - the help text could be improved some more to 
signal that certain specialized config options are only available under 
CONFIG_EMBEDDED.

	Ingo
--
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/