From: Isidore Ducasse <ducasse.isidore@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: Baselayout 2 (Was: Sun and GPL)
Date: Wed, 30 May 2007 09:43:43 +0200 [thread overview]
Message-ID: <20070530094343.4973b1fc@Bazaar> (raw)
In-Reply-To: <7a329d910705292138k76ece020gdf1d226405cb1fff@mail.gmail.com>
le Tue, 29 May 2007 21:38:17 -0700
"Wil Reichert" <wil.reichert@gmail.com> a écrit:
> On 5/29/07, Joshua Hoblitt <jhoblitt@ifa.hawaii.edu> 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"...
>
> 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.
>
I'm "afraid" it isn't. Try zcat initramfs | cpio -t . initramfs are cpio archives. And genkenrel is such a wild beast, that it compiles a static busybox against uclibc _if_ you have an uclibc toolchain available for your arch through crossdev (this feature really impresses me). If I'm not wrong, when you haven't got any such toolchain, it uses a prebuilt version of busybox. Those informations were gathered empirically by using genkernel. Could someone confirm/infirm/precise?
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2007-05-30 7:53 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 19:07 [gentoo-amd64] Can I run a complete desktop remotely? Mark Knecht
2007-05-26 19:37 ` Olivier Crête
2007-05-27 15:40 ` Mark Knecht
2007-05-27 15:56 ` Peter Davoust
2007-05-27 16:04 ` Richard Freeman
2007-05-27 16:56 ` YoYo Siska
2007-05-26 19:49 ` Aleksey Kunitskiy
2007-05-26 19:53 ` Conway S. Smith
2007-05-26 20:29 ` Simon Cooper
2007-05-26 22:24 ` Conway S. Smith
2007-05-26 21:47 ` Nuitari
2007-05-26 22:20 ` [gentoo-amd64] " Duncan
2007-05-27 0:00 ` Duncan
2007-05-26 22:51 ` [gentoo-amd64] " Conway S. Smith
2007-05-27 6:48 ` Joerg Gollnick
2007-05-27 10:57 ` Richard Freeman
2007-05-27 11:11 ` [gentoo-amd64] Sun and GPL Isidore Ducasse
2007-05-27 23:32 ` [gentoo-amd64] " Duncan
2007-05-28 0:41 ` Isidore Ducasse
2007-05-28 3:42 ` Wil Reichert
2007-05-28 6:12 ` Naga
2007-05-28 3:56 ` Boyd Stephen Smith Jr.
2007-05-28 9:25 ` Richard Freeman
2007-05-28 10:42 ` Boyd Stephen Smith Jr.
2007-05-28 10:56 ` robert burrell donkin
2007-05-28 11:52 ` Duncan
2007-05-28 16:23 ` Hemmann, Volker Armin
2007-05-28 17:28 ` Nuitari
2007-05-28 11:14 ` Duncan
2007-05-28 13:14 ` Conway S. Smith
2007-05-28 17:46 ` Duncan
2007-05-28 18:38 ` [gentoo-amd64] Baselayout 2 (Was: Sun and GPL) Sebastian Redl
2007-05-28 22:56 ` [gentoo-amd64] " Duncan
2007-05-29 0:50 ` Wil Reichert
2007-05-30 0:33 ` Florian D.
2007-05-30 4:09 ` Joshua Hoblitt
2007-05-30 4:38 ` Wil Reichert
2007-05-30 7:39 ` Duncan
2007-05-30 7:43 ` Isidore Ducasse [this message]
2007-05-30 22:57 ` Joshua Hoblitt
2007-05-30 9:12 ` Florian D.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070530094343.4973b1fc@Bazaar \
--to=ducasse.isidore@gmail.com \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox