linux-kernel - Re: Patches for REALLY TINY 386 kernels

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:	Wed, 18 Jul 2007 20:29:27 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Andi Kleen <andi@...stfloor.org>
cc:	"H. Peter Anvin" <hpa@...or.com>,
	Jonathan Campbell <jon@...dgrounds.com>,
	linux-kernel@...r.kernel.org, torvalds@...nsmeta.com
Subject: Re: Patches for REALLY TINY 386 kernels

On Jul 18 2007 20:20, Andi Kleen wrote:
>> 
>> Well, how big the vmlinux file is matters if it doesn't fit in memory
>> with enough time to get to the phase where it is dumping the init
>> sections.  
>
>If you don't have enough memory for a few tens of KB of init sections
>you're very unlikely to have enough memory for user space.

If the code was not too hackish, I would not buy that.
Routers for example can run -- minus the userspace utilities required to set
things up -- "without" userspace. Maybe someone even comes along and
writes the network interface setup as __init kernel code. If not that,
maybe a code generator. I also remember someone who posted sort of a
"kernel console" patch (same reason - to avoid userspace).

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