Hello Klondike,
+-- On Thu, 25 Sep 2014, klondike wrote --+
| Despite embedding an uncompressed initramfs, a user may want to allow for a
| compressed extra initramfs to be passed using the rd system, for example to
| boot a recovery system. Commit 9ba4bcb645898d562498ea66a0df958ef0e7a68c
| ("initramfs: read CONFIG_RD_ variables for initramfs compression") broke
| that behavior by making the choice based on CONFIG_RD_* instead of adding
| CONFIG_INITRAMFS_COMPRESSION_LZ4. Saddly, CONFIG_RD_* is also used to
| choose the supported RD compression algorithms by the kernel and a user may
| want to suppport more than one.
Ie. on embedded systems they use CONFIG_INITRAMFS_COMPRESSION_* options to
compress ram disk and on other platforms they use CONFIG_RD_* options?
| As a result the following options are added or readed affecting the embedded
| initramfs compression:
| INITRAMFS_COMPRESSION_NONE Do no compression
| INITRAMFS_COMPRESSION_GZIP Compress using gzip
| INITRAMFS_COMPRESSION_BZIP2 Compress using bzip2
| INITRAMFS_COMPRESSION_LZMA Compress using lzma
| INITRAMFS_COMPRESSION_XZ Compress using xz
| INITRAMFS_COMPRESSION_LZO Compress using lzo
| INITRAMFS_COMPRESSION_LZ4 Compress using lz4
I haven't tested the patch yet, but does it preserve the CONFIG_RD_*
options' functionality?
Would unifying the two options into one be a good idea?
--
- P J P
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
