documentation "out there" (was Re: kernel-source vs. kernel-sourcecode (please revert))

[Joe Christy]

   Vis-a-vis Aaron's note of 06/15/2004 11:18 AM:
> Arjan van de Ven wrote:
> 
>> The kernel-doc documentation explains it for 2.6,
>> if your module is called foo.c you make a Makefile with
>> obj-m := foo.o
>> in it, and do
>> make -C /lib/modules/`uname -r`/build SUBDIRS=$PWD modules
>> to build your module.
>>  
>>
> 
> Arjan --
> 
> Where is that? [root at burton kernel-doc-2.6.6]#
> [root at burton kernel-doc-2.6.6]#  fgrep -li "make -C /lib/modules/`uname 
> -r`/build" *
> [root at burton kernel-doc-2.6.6]#  fgrep -li "make -C /lib/modules/" *
> [root at burton kernel-doc-2.6.6]#  fgrep -i "/lib/modules/" *
> stallion.txt:pre-built driver modules in /lib/modules/X.Y.Z/misc for the 
> kernel in use.
> [root at burton kernel-doc-2.6.6]#
> 
> 
> I'm happy to know there's documentation "out there" that explains this, 
> but I can't find it.
> 

Look in:
	/usr/share/doc/kernel-doc-2.6.6/kbuild/modules.txt

Now, what I'd like to know, having correctly modified my module's 
Makefile and painlessly built it for my newly yum updated kernel RPM, is:
What is the correct way to install an external module in such a way as 
to regenerate all the neccessary modules.* in /lib/modules/`uname -r`. 
I've tried googling but keep getting instructions on building a whole 
custom kernel.