| 1 |
le Tue, 29 May 2007 21:38:17 -0700 |
| 2 |
"Wil Reichert" <wil.reichert@×××××.com> a écrit: |
| 3 |
|
| 4 |
> On 5/29/07, Joshua Hoblitt <jhoblitt@××××××××××.edu> wrote: |
| 5 |
> > On Wed, May 30, 2007 at 02:33:18AM +0200, Florian D. wrote: |
| 6 |
> > > FYI, genkernel is creating an initrd, not an initramfs, which is the |
| 7 |
> > preferred way nowadays. |
| 8 |
> > > Information on how to setup an initramfs can be found at: |
| 9 |
> > > http://lldn.timesys.com/docs/initramfs |
| 10 |
> > |
| 11 |
> > Umm, I think you need to check your facts. genkernel creates a gzip'd |
| 12 |
> > CPIO archive named "initramfs-genkernel-arch-versionstring"... |
| 13 |
> |
| 14 |
> So the command 'genkernel initrd' creates a file called |
| 15 |
> 'initramfs-...' which contains files called etc/initrd.defaults and |
| 16 |
> etc/initrd.scripts. Poor naming conventions but it looks like an |
| 17 |
> initrd to me. |
| 18 |
> |
| 19 |
|
| 20 |
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? |
| 21 |
-- |
| 22 |
gentoo-amd64@g.o mailing list |
Archives