linux-kernel - Re: [Announce] Linux-tiny project revival

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]

Date:	Thu, 20 Sep 2007 00:29:29 +0200
From:	Michael Opdenacker <michael@...e-electrons.com>
To:	Tim Bird <tim.bird@...sony.com>
CC:	Valdis.Kletnieks@...edu, Andi Kleen <andi@...stfloor.org>,
	linux kernel <linux-kernel@...r.kernel.org>,
	linux-tiny <Linux-tiny@...enic.com>,
	CE Linux Developers List <celinux-dev@...e.celinuxforum.org>,
	john cooper <john.cooper@...rd-harmonic.com>,
	Matt Mackall <mpm@...enic.com>
Subject: Re: [Announce] Linux-tiny project revival

Tim Bird wrote:
> Valdis.Kletnieks@...edu wrote:
>   
>> Is anybody working on testing that the patchkit "does no harm" for bigger
>> boxes (laptops, desktops, servers)? 
>>     
> Not to my knowledge.  Most of the things it provides are
> only activated by config options.  So my sense is that just
> applying the patches should be harmless.  But we'll need some
> runtime testing to see what affect some of these have on
> big iron.
>   
Tim is right, Linux-Tiny features are only activated by configuration
options.

However, that doesn't prevent us from proposing size reduction changes
impacting all kernel users, in cases a configuration option doesn't make
sense. Extensive testing in the -mm tree will then be required.

Cheers,

    Michael.

-- 
Michael Opdenacker
http://free-electrons.com
+33 621 604 642

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