Building kernel on non-Fedora systems
The kernel building wiki pages (http://wiki.laptop.org/go/Rebuilding_OLPC_kernel and http://wiki.laptop.org/go/Kernel_Building) suggest that the only way to build an OLPC kernel is using Fedora Core 6 or 7. This is quite limiting for people like me who don't use Fedora regularly as we would have to dual-boot Fedora or install it in a VM just to build kernels, while most Linux distros are perfectly capable of building a normal kernel. Has any work been done on removing the dependency on Fedora Core for kernel building? Can someone provide a brief list of the reasons for this dependency so that those interested in fixing it can do so? I realize that it would still be necessary to have RPM installed to create an RPM for quick deployment on an XO, but it should be easy to at least make the kernel binary and perhaps even the initrd image without RPM. Being able to build the kernel binary seems to be sufficient for most development purposes as a developer could just add the new binary to /boot and update the /boot/vmlinuz symlink or update olpc.fth. Denver ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Building kernel on non-Fedora systems
Denver Gingerich wrote: Has any work been done on removing the dependency on Fedora Core for kernel building? Can someone provide a brief list of the reasons for this dependency so that those interested in fixing it can do so? Michael stone pointed me at the kernels existing 'make binrpm-pkg' one evening and using the olpc config file I used this to create an rpm on a debian ubuntu system without any of the Fedora stuff. This kernel booted fine and ran fine. The problems I had were in the modules. I was not able to get the depmod to quit whining but later conversations with mstone showed that I was probably not running the right depmod command. My testing only needed stuff that was static so I didn't care at the time. without RPM. Being able to build the kernel binary seems to be sufficient for most development purposes as a developer could just add the new binary to /boot and update the /boot/vmlinuz symlink or update olpc.fth. /boot is not really /boot . :) /boot is really '/versions/boot/current/boot'. you must put your kernel there or it won't be used. -- Richard Smith [EMAIL PROTECTED] One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
