From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1HtX3I-0004DW-Lu for garchives@archives.gentoo.org; Wed, 30 May 2007 22:54:01 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l4UMptgN006060; Wed, 30 May 2007 22:51:55 GMT Received: from moa.ifa.hawaii.edu (moa.IfA.Hawaii.Edu [128.171.168.48]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l4UMprFX006055 for ; Wed, 30 May 2007 22:51:54 GMT Received: by moa.ifa.hawaii.edu (Postfix, from userid 1041) id 95801B3403; Wed, 30 May 2007 12:57:32 -1000 (HST) Date: Wed, 30 May 2007 12:57:32 -1000 From: Joshua Hoblitt To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] Re: Baselayout 2 (Was: Sun and GPL) Message-ID: <20070530225732.GA27296@ifa.hawaii.edu> References: <20070528024149.4f6d918c@Bazaar> <20070528071415.415b75f1@mandalor.homelinux.net> <465B2189.9010008@getdesigned.at> <7a329d910705281750k36fda655h899d1a3dc4dd2cb@mail.gmail.com> <465CC64E.6010004@gmx.at> <20070530040936.GE8469@ifa.hawaii.edu> <7a329d910705292138k76ece020gdf1d226405cb1fff@mail.gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EVF5PPMfhYS0aIcm" Content-Disposition: inline In-Reply-To: <7a329d910705292138k76ece020gdf1d226405cb1fff@mail.gmail.com> X-Archives-Salt: c5ad0627-0c52-440c-bc18-65f3586b8626 X-Archives-Hash: 63065290eaaf8883f4889473fa99895f --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable The terminilogy of initramfs/initrd is used pretty lossely, even by kernel devs. My understanding is that typically 'initrd' is refering to an actual filesystem image (created on a loopback) and get's mounted a a ramdisk and used at the root filesystem. Where as an initramfs image is just a CPIO archive that gets unpacked into a tmpfs filesystem that is then mounted as root. initramfs images can be either built into the kernel image or loaded from an external file. Byeond the format there's not much difference bewteen them. In theory an initramfs iamge could be a bit smaller as it doesn't have to drag around the filesystem metadata with it. Also, as it's just a CPIO archive a driver for the filesystem type need not be built into the kernel. Wikipedia considers initramfs & initrd to refer to the same thing: http://en.wikipedia.org/wiki/Initrd Cheers, -J -- On Tue, May 29, 2007 at 09:38:17PM -0700, Wil Reichert wrote: > On 5/29/07, Joshua Hoblitt wrote: > >On Wed, May 30, 2007 at 02:33:18AM +0200, Florian D. wrote: > >> FYI, genkernel is creating an initrd, not an initramfs, which is the > >preferred way nowadays. > >> Information on how to setup an initramfs can be found at: > >> http://lldn.timesys.com/docs/initramfs > > > >Umm, I think you need to check your facts. genkernel creates a gzip'd > >CPIO archive named "initramfs-genkernel-arch-versionstring"... >=20 > So the command 'genkernel initrd' creates a file called > 'initramfs-...' which contains files called etc/initrd.defaults and > etc/initrd.scripts. Poor naming conventions but it looks like an > initrd to me. >=20 > Wil > --=20 > gentoo-amd64@gentoo.org mailing list >=20 --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFGXgFcWa2BU+b7tU0RAtIKAJ9J729pzGT4zauvlxTak7wOq4nUigCfSC3a nlpxS9pPAFNvQ6l8+tj7MkU= =KCk8 -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm-- -- gentoo-amd64@gentoo.org mailing list