| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Tue, 2 Nov 2010 08:26:59 +0000 From: trapDoor <trapdoor6@...il.com> To: LKML <linux-kernel@...r.kernel.org> Subject: Pure kernel '2.6.37-rc1-00001-ge99d11d' shown as ~-dirty after compilation ,Hello, When I run 'make kernelrelease' on freshly cloned Linus' git tree it shows kernel version as: '2.6.37-rc1-00001-ge99d11d' - and that's correct. But after compilation it turned up '2.6.37-rc1-00001-ge99d11d-dirty'. I didn't apply any custom patches to my local tree between 'make kernelrelease' and compilation. What I only added - and before running 'make kernelrelease' - were the following Radeon firmware blobs for my graphic card, which I placed in <kernel-source>/firmware/radeon/, in order to compile them in: REDWOOD_me.bin REDWOOD_pfp.bin REDWOOD_rlc.bin That's how I always did and none of the git-kernels I compiled before was referred to as '-dirty' due to the firmware blobs added manually. Also, the kernel version shown by 'make kernelrelease' never differed from the final kernel version after compilation. Of course assuming that no patches were applied in the meantime and no extra string was appended manually to the kernel version. So, what's this '-dirty' about? -- Thanks, Tomasz -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists