On Mon, Dec 11, Arjan van de Ven wrote: > strings doesn't work there, it's a compressed image! Thats why get_kernel_version calls gzip. > also... can't you just know which vmlinux it is in the first place? No, you cant. > (or in other words, why is SLES the only one with the problem?) Everyone has this "problem". Or how do you know what kernelrelease is inside a random ELF or bzImage binary? - 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/
- Follow-Ups:
- Re: 2.6.19-git13: uts banner changes break SLES9 (at least)
- From: Jan Engelhardt <jengelh@linux01.gwdg.de>
- Re: 2.6.19-git13: uts banner changes break SLES9 (at least)
- From: Arjan van de Ven <arjan@infradead.org>
- Re: 2.6.19-git13: uts banner changes break SLES9 (at least)
- References:
- 2.6.19-git13: uts banner changes break SLES9 (at least)
- From: Andy Whitcroft <apw@shadowen.org>
- Re: 2.6.19-git13: uts banner changes break SLES9 (at least)
- From: Olaf Hering <olaf@aepfle.de>
- Re: 2.6.19-git13: uts banner changes break SLES9 (at least)
- From: Linus Torvalds <torvalds@osdl.org>
- Re: 2.6.19-git13: uts banner changes break SLES9 (at least)
- From: Olaf Hering <olaf@aepfle.de>
- Re: 2.6.19-git13: uts banner changes break SLES9 (at least)
- From: Arjan van de Ven <arjan@infradead.org>
- Re: 2.6.19-git13: uts banner changes break SLES9 (at least)
- From: Olaf Hering <olaf@aepfle.de>
- Re: 2.6.19-git13: uts banner changes break SLES9 (at least)
- From: Arjan van de Ven <arjan@infradead.org>
- 2.6.19-git13: uts banner changes break SLES9 (at least)
- Prev by Date: Re: 2.6.19-git13: uts banner changes break SLES9 (at least)
- Next by Date: Re: Status of buffered write path (deadlock fixes)
- Previous by thread: Re: 2.6.19-git13: uts banner changes break SLES9 (at least)
- Next by thread: Re: 2.6.19-git13: uts banner changes break SLES9 (at least)
- Index(es):
![]() |