Date: Thu, 21 Aug 2003 19:31:13 -0300
From: Werner Almesberger <wa@almesberger.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: "Bryan O'Sullivan" <bos@serpentine.com>, gkajmowi@tbaytel.net,
       linux-kernel@vger.kernel.org
Subject: Re: Initramfs
Message-ID: <20030821193113.A3448@almesberger.net>
References: <200308210044.17876.gkajmowi@tbaytel.net> <1061447419.19503.20.camel@camp4.serpentine.com> <3F44D504.7060909@pobox.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3F44D504.7060909@pobox.com>; from jgarzik@pobox.com on Thu, Aug 21, 2003 at 10:19:48AM -0400
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1010
Lines: 28

Jeff Garzik wrote:
> Support replacing "initrd=" with "initramfs=", so that bootloaders can 
> pass a cpio image into the standard initrd memory space.

This sounds like a very good idea, yes.

Or, maybe even make it such that initramfs acts like a file system,
that will just de-cpio the content of a block device to a ramfs.

Pro:
 - requires less or no changes to existing initrd
 - one can experiment with initramfs loaded from other sources than
   an initrd

Contra: 
 - needs more infrastructure than plain initramfs

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, Buenos Aires, Argentina         wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
-
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/