Jim McQuillan wrote:
3. build the kernel, install all possible NICs inside the kernel
4. Run mkinitrd from the ltsp-initrd tools
5. gunzip the initrd for the new kernel, edit linuxrc to not look for network
modules, gzip it back up
If you are adding the nic drivers as statically linked, rather than as
modules, then you don't really need the initrd at all. You can just
have the kernel do the ip-autoconfig and nfs-root for you. Although
keep in mind, Linus keeps threatening to remove those items from the
kernel.
I was getting an error without the initrd. Something like, something
too big for memory address. I'll have to try it again.
And that's about it. That's probably wrong on a lot of levels, but it works.
I still haven't figured out how to get modules working on there, even if I
copy over /lib/modules/`uname -r` to /opt/ltsp/i386, they still won't load.
I'm probably missing something in linuxrc somewhere.
Hmm, dunno. What version of the kernel are you using, and what version
of LTSP?
2.6.12 of the kernel, the initrd kit might be an older one, mine is
v3.0.15, I downloaded it off SF.
Is there a newer one in LBE?
Steve
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_____________________________________________________________________
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.freenode.net
