From mboxrd@z Thu Jan  1 00:00:00 1970
From: greg@kroah.com (Greg KH)
Date: Mon, 13 Mar 2017 16:32:39 +0800
Subject: cannot insmod sculld in ldd3
In-Reply-To: <00355f0a-57da-e530-2ada-94b5eb9faeff@gmail.com>
References: <CAJxZdtF9eFeY=pExHBLFe+b1DuSJeEZHpD7Fq5Tuqg5VW3naSQ@mail.gmail.com>
	<20170312190304.GA10105@kroah.com>
	<00355f0a-57da-e530-2ada-94b5eb9faeff@gmail.com>
Message-ID: <20170313083239.GA26006@kroah.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

On Mon, Mar 13, 2017 at 12:19:58PM +0800, Freeman Zhang wrote:
> Hi Greg,
> 
> 
> On 3/13/17 3:03 AM, Greg KH wrote:
> 
> > 
> > 'depmod' handles all of this when you install a kernel and its modules.
> > 
> 
> Thanks for that information, now I take 'depmod' seriously and stop
> making up inelegant methods. I studied the 'kmod', both its behaviors
> and codes, and got plenty of ideas about module symbol stuff.
> 
> However, I am still wondering why copy Module.symvers file works too, at
> building time?

Because that is what depmod creates, you probably didn't change much, if
anything, from the kernel version you copied it from.  But don't do
that, it is probably wrong.

thanks,

greg k-h