Re: [PATCH] LKCD for 2.5.44 (7/8): dump configuration

From: Matt D. Robinson (yakker@aparity.com)
Date: Wed Oct 23 2002 - 12:54:13 EST

Because the zlib code option CONFIG_ZLIB_DEFLATE won't be set
to 'n' if the option isn't reset properly. That means if you
set CONFIG_CRASH_DUMP_COMPRESS_GZIP and then not set it back
explicitly, the CONFIG_ZLIB_DEFLATE option doesn't get set to
'n' properly.

We explored a number of options, but this guarantees that the
zlib code doesn't get built if it doesn't have to.

--Matt

On Wed, 23 Oct 2002, Christoph Hellwig wrote:
|>On Wed, Oct 23, 2002 at 02:44:55AM -0700, Matt D. Robinson wrote:
|>> +else
|>> + define_tristate CONFIG_CRASH_DUMP_BLOCKDEV n
|>> + define_tristate CONFIG_CRASH_DUMP_COMPRESS_RLE n
|>> + define_tristate CONFIG_CRASH_DUMP_COMPRESS_GZIP n
|>
|>What's the reason for this?
|> 

-- 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

This archive was generated by hypermail 2b29 : Wed Oct 23 2002 - 22:01:05 EST