Nathan Paul Simons wrote: > kernel configs with the same kernel version. Since you will probably be > changing the EXTRAVERSION variable anyway (to differentiate between different How about addining an additional item to the config scripts: a "build id". This can be any random string. It just gets statically compiled into the kernel, and is retrieved via `cat /proc/build-id` or whatever. This will allow users to match up a running kernel with its config data, without actually cramming the data into the kernel. -M - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: [PATCH] 2.2: /proc/config.gz Arjan van de Ven
- Re: [PATCH] 2.2: /proc/config.gz Chip Salzenberg
- Re: [PATCH] 2.2: /proc/config.gz Pavel Machek
- Re: [PATCH] 2.2: /proc/config.gz Jamie Lokier
- Re: [PATCH] 2.2: /proc/config.gz Michael Elizabeth Chastain
- Re: [PATCH] 2.2: /proc/config.gz Alan Cox
- Re: [PATCH] 2.2: /proc/config.gz almesber
- Re: [PATCH] 2.2: /proc/config.gz almesber
- Re: [PATCH] 2.2: /proc/config.... Alan Cox
- Re: [PATCH] 2.2: /proc/co... Nathan Paul Simons
- Re: [PATCH] 2.2: /pro... Michael Rothwell
- Re: [PATCH] 2.2: /pro... Daniel Phillips
- Re: [PATCH] 2.2: /pro... Timur Tabi
- Re: [PATCH] 2.2: /pro... Andi Kleen
- Re: [PATCH] 2.2: /pro... Jan-Benedict Glaw
- Re: [PATCH] 2.2: /pro... almesber
- Re: [PATCH] 2.2: /pro... Andi Kleen
- Re: [PATCH] 2.2: /pro... almesber
- Re: [PATCH] 2.2: /pro... Andi Kleen
- Re: [PATCH] 2.2: /pro... Alan Cox
- Re: [PATCH] 2.2: /pro... Werner Almesberger