On Mon, Dec 11, Linus Torvalds wrote: > "Suppose I send you some random vmlinux binary." > > THAT is the problem. Erm no, thats reality and happens every day. git-bisect a modular kernel on one box and test it on another. The mkinitrd (and depmod) wants to know where to look for modules. Of course I could tell it every time what the kernelrelease is, but why do I have to? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] 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: Linus Torvalds <[email protected]>
- 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 <[email protected]>
- Re: 2.6.19-git13: uts banner changes break SLES9 (at least)
- From: Olaf Hering <[email protected]>
- Re: 2.6.19-git13: uts banner changes break SLES9 (at least)
- From: Linus Torvalds <[email protected]>
- Re: 2.6.19-git13: uts banner changes break SLES9 (at least)
- From: Olaf Hering <[email protected]>
- Re: 2.6.19-git13: uts banner changes break SLES9 (at least)
- From: Linus Torvalds <[email protected]>
- 2.6.19-git13: uts banner changes break SLES9 (at least)
- Prev by Date: [2.6 patch] usbvision: possible cleanups
- Next by Date: [-mm patch] make sysrq_always_enabled_setup() static
- 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):
 |