> It isn't complete yet, because off the following unresolved topics:
> 1. For the moment it only supports files,dirs and symlinks.
> 2. It still needs the "RAM disk" and "initrd" support compiled in the Kernel.
> 3. I haven't tried to support hardlinks.
> 4. Since i use the ramdisk for decompression the cpio image must be a
> multiple of BLOCK_SIZE bytes.
> 5. The cpio crc field is ignored.
Uhh.... Why? I can post initramfs patches tonight - unpacking and populating
initramfs is trivial and I can't think of any reason why initrd would be
useful here (BTW, you could have picked uncpio code from l-k posting -
3Kb, deals with links properly, doesn't mess with ramdisk at all).
Anyway, the real problem with iniramfs is on the build side. I.e. what
do we want in makefiles for early userland/what do we want to use as
Until that is done the ungzip/uncpio part is pretty much pointless... It
can go into the kernel anytime, but what would it give us if we don't have
stuff to put in there?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/