So are you saying that if I copy my .config file into the linux source directory and then re-tar.gz it, and then run "make kernel" (from where? the top directory of the systemimager source tree?) then that will make the kernel with all the patches and with the drivers i need built in?
thanks, Kristina On Mon, Aug 23, 2004 at 12:02:04PM -0700, Peter Mueller wrote: - You need to apply the patches to the kernel. My list, which is 3-4 months - old, currently has: - - linux.alpha.81hardcode_rd_blocksize.patch - linux.alpha.config - linux.i386.90bcm5700.patch - linux.i386.91bcm5700_fixup.patch - linux.i386.99kernel-name.patch - linux.i386.99optimize.patch - linux.i386.config - linux.i386,parisc.81hardcode_rd_blocksize.patch - linux.ia64.05ia64.patch - linux.ia64.15blkioctl-sector.patch - linux.ia64.81hardcode_rd_blocksize.patch - linux.ia64.85optimize_for_size.patch - linux.ia64.config - linux.parisc.05pa0.patch - linux.parisc.config - linux.ppc.10pre4.patch - linux.ppc64.10ppc64.patch - linux.ppc64.11ppc64-3.patch - linux.ppc64.90cramfs.patch - linux.ppc64.config - linux.ppc64-iSeries.10ppc64.patch - linux.ppc64-iSeries.11ppc64-3.patch - linux.ppc64-iSeries.90cramfs.patch - linux.ppc64-iSeries.config - linux.ppc.config - - You should be using the systemimager Makefile to "make kernel" to put all - these patches in for you. First get your .config put into your linux.tar.gz - file. Once you have the kernel with all modules compiled directly in, you - can use the existing initrd.img and boel_binaries instead of having to - compile all that yourself. Since boel_binaries takes forever to compile, - this is a significant timesavings. - - If you get stuck, send me your .config and I will compile a kernel for you. - - Regards, - - P - - ________________________________ - - From: [EMAIL PROTECTED] on behalf of K. Clair - Sent: Mon 8/23/2004 9:26 AM - To: [EMAIL PROTECTED] - Subject: [Sisuite-users] using mkbootpackage for custom kernel - - - - Hello, - - I am trying to make a kernel that I can use to autoinstall clients with - no floppy drives and with SCSI disks. - - I discovered the "unofficial" program mkbootpackage, and it seems like - it would be useful to me. - - What I have done so far is to download the systemimager 3.2.3 source, - copied the config from the /boot/i385/standard directory to .config - in the kernel source directory in the systemimager source tree, changed - the option from "m" to "y" on the SCSI and network drivers I need, and - compiled a new kernel using make oldconfig. - Does this sound ok so far? :) - - Now I have read the documentation from mkbootpackage (--help), and I'm - confused by the --modules option. Because here it seems to indicate - that I could leave the SCSI drivers as modules and indicate them as - options to --modules when I run mkbootpackage. Is this true, or am I - misunderstanding that? - - Thanks for any info on this subject, - Kristina Clair - - - ------------------------------------------------------- - SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media - 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 - Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. - http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 - _______________________________________________ - Sisuite-users mailing list - [EMAIL PROTECTED] - https://lists.sourceforge.net/lists/listinfo/sisuite-users - - ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
