Kernel Newbies archive on lore.kernel.org
 help / color / Atom feed
From: Aruna Hewapathirane <aruna.hewapathirane@gmail.com>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
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: Sat, 11 May 2019 09:20:22 -0400
Message-ID: <CAFSeFg9km1j0YNavXB8dPdaPmOu-nM3h4dFS7e=o_GwLwaHusw@mail.gmail.com> (raw)
In-Reply-To: <7229.1557547129@turing-police>

[-- Attachment #1.1: Type: text/plain, Size: 1070 bytes --]

On Fri, May 10, 2019 at 11:58 PM Valdis Klētnieks <valdis.kletnieks@vt.edu>
wrote:

> 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
>

Seriously ? Since when are you working for turing-police ? But yes
agreed...  at least it gives someone a
reasonably sane path to follow... nothing lost in trying right :)


> 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.
>
Agreed.

[-- Attachment #1.2: Type: text/html, Size: 1660 bytes --]

<div dir="ltr"><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 10, 2019 at 11:58 PM Valdis Klētnieks &lt;<a href="mailto:valdis.kletnieks@vt.edu">valdis.kletnieks@vt.edu</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Fri, 10 May 2019 22:11:31 -0400, Aruna Hewapathirane said:<br>
<br>
&gt; &gt; Suppose I have two kernels, one is A.B.C build by people Tom. And<br>
&gt; &gt; the other is A.B.C build by Jerry. The source code have been deleted<br>
<br>
&gt; Run diff vmlinuz-Tom vmlinuz-Jerry and see if they differ. Then just  to<br>
<br>
Don&#39;t even bother.  If Tom and Jerry both did builds, the binaries *will* differ, because...<br>
<br>
% dmesg | grep &#39;Linux vers&#39;<br>
[    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<br></blockquote><div><br></div><div>Seriously ? Since when are you working for turing-police ? But yes agreed...  at least it gives someone a <br></div><div>reasonably sane path to follow... nothing lost in trying right :)<br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
There&#39;s a datestamp, a build number, and a compiler version in there.<br>
<br>
Also, since vmlinuz is a binary file, /bin/cmp is a better choice than diff.<br></blockquote><div>Agreed. <br></div><div><br></div><div><br></div><div><br></div><div> </div></div></div>

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply index

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-08  8:52 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
2019-05-11 13:20     ` Aruna Hewapathirane [this message]
2019-05-11 13:53       ` Valdis Klētnieks
2019-05-11 23:47         ` chiachen

Reply instructions:

You may reply publically 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='CAFSeFg9km1j0YNavXB8dPdaPmOu-nM3h4dFS7e=o_GwLwaHusw@mail.gmail.com' \
    --to=aruna.hewapathirane@gmail.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=valdis.kletnieks@vt.edu \
    --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

Kernel Newbies archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/kernelnewbies/0 kernelnewbies/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 kernelnewbies kernelnewbies/ https://lore.kernel.org/kernelnewbies \
		kernelnewbies@kernelnewbies.org kernelnewbies@archiver.kernel.org
	public-inbox-index kernelnewbies

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernelnewbies.kernelnewbies


AGPL code for this site: git clone https://public-inbox.org/ public-inbox