Jim, thanks again for your help. Copying the /lib/modules/2.4.19 tree over solved the problem, I didn't even need to run depmod as the modules.dep file was already there, it seems to be created as part of the "make modules_install" target during the kernel compilation phase.

This step is indeed missing from the parallel dhcp recipe, but I have to say that otherwise the recipe is complete and we're now running with no interference from or to the exisiting dhcp server. Thanks again!

-John

John,

The fact that your root/lib/modules is empty is normal.

The buildk script will create a ramdisk filesystem, copy
the contents of the ltsp_initrd_kit/root into that new ram
filesystem. It will then copy the modules from /lib/modules/2.4.19,
and it will create the modules.dep file.

Then, that ram based filesystem will be saved as a file, and
tacked onto the end of the kernel, and the kernel will be
tagged for Etherboot using the mknbi-linux command.

What I think you didn't do was copy the /lib/modules/2.4.19
tree over to /opt/ltsp/i386/lib/modules. Perhaps the recipe doesn't
say to do that. I haven't tried following that recipe, because
I don't have multiple dhcp servers.

Also, once you copy the modules, you'll need to run depmod on
them, to create the modules.dep file. take a look at the buildk
script, to see how depmod is being run when the initrd is build.
the process is similar.

Hope that helps,

Jim McQuillan
[EMAIL PROTECTED]



-------------------------------------------------------
This sf.net email is sponsored by: viaVerio will pay you up to
$1,000 for every account that you consolidate with us.
http://ad.doubleclick.net/clk;4749864;7604308;v?
http://www.viaverio.com/consolidator/osdn.cfm
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
     https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.openprojects.net

Reply via email to