Re: [Etherboot-users] Re: Finding modules dependencies

[David Leunen <leunen.d@fsagx.ac.be>]

> >1) First for your clients, decide which modules you need (normally a
> >   static kernel would do it for the first tests). 

I'm not very confident with linux or kernel compilation. So I don't
really know which modules I need :-}


>You can install the clients' modules without interfering with the server
> modules by using the INSTALL_MOD_PATH variable in the Makefile like
> this:
> 
> In the client kernel source directory:
> 
>         make config     (or menuconfig or xconfig)
>         # remembering to select the NIC driver compiled in, NFSroot,
>         # Kernel IP autoconfig, and BOOTP/DHCP support
>         make dep clean bzImage modules
>         make INSTALL_MOD_PATH=/tftpboot/client modules_install
>         mknbi-linux --output=/tftpdir/client.nb arch/i386/boot/bzImage

Well, I almost did that (make mrproper menuconfig dep bzImage modules
modules_install). I tagged the image into --output=/tftpboot/kernel. I
copied the /lib directory to /tftpboot/10.0.0.x . This /lib contain 3
dir for the 3 release installed. I don't have any modules.dep in the
client dir (/lib/2.2.14) !!

The thing is that the client go for /boot/kernel-2.2.12smp (which is the
server one!) during the boot process. It also find the modules in the
wrong directory. However, I'm sure that I compiled the kernel in the
right directory (/usr/src/linux-2.2.14).


> The /tftpdir is not a typo. I keep the tftp directory separate from the
> NFSroot.

I don't understand this sentence.


> >2) Save your kernel configuration .config for your terminals

What for?


>>Build a new (SMP) kernel for your server (make dep clean bzlilo modules
>>   modules_install)
>
>And then repeat in the server kernel source directory, without selecting
> the diskless client features. Or just use the distribution provided
> kernel if you don't need special features.

Do I really need to recompile the server kernel? It works now.

 
> I also use lndir (from the X tools) to create a tree of symbolic links
> so that I can share one kernel source tree across the client and server
> compile trees, but that's a different story and you don't need this
> complication at the moment.

Yes, I don't understand...
===========================================================================
This Mail was sent to netboot mailing list by:
David Leunen <leunen.d@fsagx.ac.be>
To get help about this list, send a mail with 'help' as the only string in
it's body to majordomo@baghira.han.de. If you have problems with this list,
send a mail to netboot-owner@baghira.han.de.