Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Compiling a custom kernel vs. compiling a single module.



jbk wrote:
> I began to compiling custom kernels a long time ago first for the fun of 
> it and to see how small I could make it for my purposes. Then I added a 
> tape drive and have been making custom Fedora kernels to enable that 
> module.
> Since the Fedora kernel is updated so frequently and enables most 
> features I want and the usb devices becoming so wide ranging, I no 
> longer want to bother trying to reduce the kernel size, but I still need 
> to compile the ide-tape module. So, what is the procedure to compile one 
> or two additional modules for the running kernel?
> The kernel-devel package is for that purpose. I see when I run 'make 
> help' that there is a target called '/dir/file.ko'. So do I just run 
> 'make /drivers/ide/ide-tape.ko' and then make 'modules install', or are 
> there some other steps? What if I want to make three or four modules? Do 
> I just separate the different targets with a space after make?
> I know I could just try hacking away at it but I am also interested in 
> the discussion and any insight others may have.
> Jim K-R
> 

You could start by looking at VMWare Workstation's vmware-config.pl.
Whenever I update the kernel on my laptop, I have to re-run this to
recompile the vmware kernel modules against the new kernel's sources.


-- 
John Abreau
IT Manager
Zuken USA
238 Littleton Rd., Suite 100
Westford, MA 01886
T: 978-392-1777            F: 978-692-4725
M: 978-764-8934
E: John.Abreau at zuken.com  W: www.zuken.com




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org