From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Aruna Hewapathirane <aruna.hewapathirane@gmail.com>
Cc: wuzhouhui <wuzhouhui14@mails.ucas.ac.cn>,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: how to determine whether the source code is same between two kernels
Date: Fri, 10 May 2019 23:58:49 -0400 [thread overview]
Message-ID: <7229.1557547129@turing-police> (raw)
In-Reply-To: <CAFSeFg9k6vkppSzRoO4viaGogC9f+89pcAsaboOaRAq5QN9V7A@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 738 bytes --]
On Fri, 10 May 2019 22:11:31 -0400, Aruna Hewapathirane said:
> > Suppose I have two kernels, one is A.B.C build by people Tom. And
> > the other is A.B.C build by Jerry. The source code have been deleted
> Run diff vmlinuz-Tom vmlinuz-Jerry and see if they differ. Then just to
Don't even bother. If Tom and Jerry both did builds, the binaries *will* differ, because...
% dmesg | grep 'Linux vers'
[ 0.000000] Linux version 5.1.0-rc5-next-20190416-dirty (source@turing-police) (gcc version 9.0.1 20190328 (Red Hat 9.0.1-0.12) (GCC)) #664 SMP PREEMPT Wed Apr 17 12:31:51 EDT 2019
There's a datestamp, a build number, and a compiler version in there.
Also, since vmlinuz is a binary file, /bin/cmp is a better choice than diff.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-05-11 3:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 8:52 how to determine whether the source code is same between two kernels wuzhouhui
2019-05-08 9:25 ` Greg KH
2019-05-08 9:43 ` wuzhouhui
2019-05-08 10:08 ` greg kh
2019-05-08 13:43 ` Valdis Klētnieks
2019-05-11 2:11 ` Aruna Hewapathirane
2019-05-11 3:58 ` Valdis Klētnieks [this message]
2019-05-11 13:20 ` Aruna Hewapathirane
2019-05-11 13:53 ` Valdis Klētnieks
2019-05-11 23:47 ` chiachen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7229.1557547129@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=aruna.hewapathirane@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=wuzhouhui14@mails.ucas.ac.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).