Sam Ravnborg wrote:
>On Tue, Jul 22, 2003 at 07:17:46PM +0100, Christoph Hellwig wrote:
>
>
>>If you really want that do it a a separate make updateconfig script instead
>>of bloating make oldconfig.
>>
>>
>
>updateconfig is definetely more acceptable than bloating oldconfig.
>But would we end up with lots of hacks - and where do we stop.
>Do we want to go the whole way back to a 2.0 .config and do an
>acceptable .config using:
>make updateconfig
>
>Or is this limited to 2.4 -> 2.6?
>
> Sam
>
>
Well there are 2 issues here:
1) How to handle "make oldconfig" on 2.4 config files. Which may not be
fixable in a manner that doesn't involve really ugly code.
2) That make menuconfig|xconfig on a clean 2.6 tree results in a kernel
that doesn't have console support. This will be something that will
come up over and over again in the future, and does not require ugly
hacks to fix.
-- Once you have their hardware. Never give it back. (The First Rule of Hardware Acquisition) Sam Flory <sflory@rackable.com>- 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 Jul 23 2003 - 22:00:47 EST