Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 9 Aug 2002 17:59:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 9 Aug 2002 17:59:45 -0400 Received: from waste.org ([209.173.204.2]:4073 "EHLO waste.org") by vger.kernel.org with ESMTP id ; Fri, 9 Aug 2002 17:59:44 -0400 Date: Fri, 9 Aug 2002 17:03:25 -0500 (CDT) From: Oliver Xymoron To: "H. Peter Anvin" cc: linux-kernel@vger.kernel.org Subject: Re: klibc development release In-Reply-To: Message-ID: 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: 1322 Lines: 30 On 8 Aug 2002, H. Peter Anvin wrote: > Okay, I'm starting to have enough guts about this to release for > testing... > > klibc is a tiny C library subset intended to be integrated into the > kernel source tree and being used for initramfs stuff. Thus, > initramfs+rootfs can be used to move things that are currently in > kernel space, such as ip autoconfiguration or nfsroot (in fact, > mounting root in general) into user space. Remind me why we'd want this in the kernel source tree when we don't even have modutils there? Or a real bootloader? There is no requirement that the kernel must be able to build a bootable image with ip autoconf and nfsroot, etc. without using external tools. A minimal 'parse command line to mount root and call real init' might be nice, but mostly as an example, like the example watchdog code. I think a better way to go is to simply roll an initbootutils.tar.gz, point to it in the kernel CHANGES, etc., start pulling stuff into it, and people will catch on in no time. -- "Love the dolphins," she advised him. "Write by W.A.S.T.E.." - 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/