Re: [SSI-devel] 2.6.8.1 build instructions
Brought to you by:
brucewalker,
rogertsang
From: Bharata B R. <bha...@hp...> - 2004-12-14 08:59:56
|
Brian, 2.6.8.1 booted fine on SuSE. Just I had to fix a minor build error: (kernel/signal.c) EXPORT_SYMBOL(ssi_check_migpending) was being done inside of #ifdef __ARCH_WANT_SYS_PAUSE, I had to move it to inside CONFIG_SSI. Regards, Bharata. On Tue, 2004-12-14 at 11:00, Brian J. Watson wrote: > Brian J. Watson wrote: > > Bharata, can you redo the test with booting an OpenSSI kernel and initrd > > on a base SuSE system, this time with the latest 2.6.8.1 kernel from the > > trunk? Of course, we now know that cluster-tools needs to be installed. > > I'll send instructions for building the 2.6.8.1 kernel in a follow-up > > e-mail. > > Hi Bharata- > > 1. Get the vanilla 2.6.8.1 kernel from kernel.org: > > http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.8.1.tar.bz2 > > 2. On your build machine, extract the base kernel source. I assume it > extracts into a directory named linux/, but it could be linux-2.6.8.1/. > > 3. Checkout the trunk of the CI and OpenSSI repositories. > > 4. Copy the contents of ci/kernel/ and openssi/kernel/ into the 2.6.8.1 > source: > > $ cp -af ci/kernel/. linux/ > $ cp -af openssi/kernel/. linux/ > > 5. cd into the linux/ directory and patch it with kdb: > > $ patch -p1 <../openssi/kernel.patches/common/kdb-common-ssi.patch > $ patch -p1 <../openssi/kernel.patches/i386/kdb-i386-ssi.patch > > 6. Edit the top-level Makefile if you wish to change the EXTRAVERSION > field, to give your kernel a unique version number. For example, > 2.6.8.1-bbr, where the EXTRAVERSION would be -bbr. > > 7. Copy openssi/kernel.config/development.i686 to .config in the linux/ > directory, and run `make oldconfig'. > > 8. Run `make' to build the kernel and modules. > > 9. Run `make modules_install INSTALL_MOD_PATH=$(pwd)/install' to create > a modules tree. Ignore the depmod warnings. > > 10. Create a tarball of the install/ directory containing your modules > tree. scp it and the kernel image (arch/i386/boot/bzImage) to your SuSE > test machine. The following steps will be on your test machine. > > 11. On your test machine, move the bzImage file to > /boot/vmlinuz-<kernel_version>. > > 12. Extract the modules tarball, and move > install/lib/modules/<kernel_version> to /lib/modules/. > > 13. Run `depmod -ae <kernel_version>' to properly setup the module > dependency files. > > 14. Create your initrd. You can do this by copying the modules tarball > to an OpenSSI for Fedora Core 2 system, executing steps 12 and 13, and > running mkinitrd there. Alternatively, you can edit the ramdisk you used > for SuSE 9.0 testing by replacing its kernel modules in lib/ with their > 2.6.8.1 equivalents. When you're done, move the initrd to > /boot/initrd-<kernel_version>.img. > > 15. Create a stanza in /etc/grub.conf that refers to your new kernel and > initrd. > > 16. Reboot with the new kernel. > > Joining a second node doesn't work with the 2.6.8.1 kernel, so there's > no need to try that, yet. > > If you're not able to finish this today, please send status at the end > of the day. > > Thanks, > > Brian > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > ssic-linux-devel mailing list > ssi...@li... > https://lists.sourceforge.net/lists/listinfo/ssic-linux-devel > |