On Tue, 20 Jul 2004, Linh Dang wrote: > > On 20 Jul 2004, wd at denx.de wrote: > >> In message <wn5zn5v8nl8.fsf at linhd-2.ca.nortel.com> you wrote: >>> >>> - I failed to see what in initramfs mechanism would prevent >>> one from having "separated images which can be updated >>> independently of each other." >> >> initramfs gets linked with the kernel into one image, similar to > > But you don't have to. What ever you can do with the good-old initrd > image you can do with the new initramfs (really cpio archive) > image. The main difference is the creation: genext2fs vs cpio. > > I just happen to use zImage.initrd (where ramdisk.image.gz is a cpio > archive) in our project because it's the most appropriate for our > situation.
i have to agree with wolfgang here -- how would you create and use an initramfs image separately from the kernel image? the only possibility i can see based on my perusal is to incorporate the initramfs into the zImage.initrd. rday ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/