Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 9 Mar 2003 06:36:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 9 Mar 2003 06:36:44 -0500 Received: from ebiederm.dsl.xmission.com ([166.70.28.69]:1065 "EHLO frodo.biederman.org") by vger.kernel.org with ESMTP id ; Sun, 9 Mar 2003 06:36:44 -0500 To: Daniel Egger Cc: Linux Kernel Mailinglist Subject: Re: [BK PATCH] klibc for 2.5.64 - try 2 References:

<20030307233916.Q17492@flint.arm.linux.org.uk> <20030308100359.A27153@flint.arm.linux.org.uk> <20030308161309.B1896@flint.arm.linux.org.uk> <1047209545.4102.3.camel@sonja> From: ebiederm@xmission.com (Eric W. Biederman) Date: 09 Mar 2003 04:46:20 -0700 In-Reply-To: <1047209545.4102.3.camel@sonja> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 966 Lines: 19 Daniel Egger writes: > Am Sam, 2003-03-08 um 18.28 schrieb Eric W. Biederman: > > > All of my policy is already in user space and as I boot over the > > network size is not a large constraint. > > Just curious, for me size *is* a large constraint just because I'm > booting over network. The size of a kernel must not exceed 1M in > size here and that brought me quite some troubles with the growth > of 2.5.x. How did you get around this? I use etherboot. It is small and has not problems acting as network bootstrap program if you are stuck with EFI. Etherboot can load to any address < 4GB and can jump to a 32bit entry point. It's not rocket science or magic just good open source code. Eric - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/