Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 11 Jan 2002 01:53:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 11 Jan 2002 01:53:36 -0500 Received: from neon-gw-l3.transmeta.com ([63.209.4.196]:14093 "EHLO neon-gw.transmeta.com") by vger.kernel.org with ESMTP id ; Fri, 11 Jan 2002 01:53:21 -0500 To: linux-kernel@vger.kernel.org From: "H. Peter Anvin" Subject: Re: [RFC] klibc requirements, round 2 Date: 10 Jan 2002 22:53:14 -0800 Organization: Transmeta Corporation, Santa Clara CA Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Disclaimer: Not speaking for Transmeta in any way, shape, or form. Copyright: Copyright 2002 H. Peter Anvin - All Rights Reserved Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Followup to: By author: "Torrey Hoffman" In newsgroup: linux.dev.kernel > > My concern is with the minority who are using initrd, and in > some cases a very customized initrd. > They can presumably use whatever they already do, except they'll make it into a .cpio.gz file instead of an .img.gz file. > The important thing, I think, is that it should be easy for > less-than-guru level hackers to add programs to the initramfs, > even if the program they want can't be linked with klibc. > > This really comes down to: What will the build process be for > these initramfs images? > > By the way, is initramfs intended to supercede initrd, or will > they co-exist? Eventually supercede; it will let us pull out an amazing amount of crud. -hpa -- at work, in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt - 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/