On Mon, 25 Apr 2005, Jeff Carr wrote: > /lib/modules/2.6.11-1-686-smp/source/ -> > /home/dilinger/src/kernel/kernel-image/2.6.11-2/kernel-image-2.6.11-i386-2.6.11/install-686-smp > > Can this be cleaned up? It would be convienent to be able to rebuild the > kernel sources & modules against stock kernel. > > Could the build process be modified so that the kernel sources are built > from /usr/src/kernel-image/2.6.11-2/ or something simple like that? bla, and again dilinger will probably rename his ~/src/kernel/kernel-image in ~/src/kernel/dont_report_a_bug_against_that_symlink.
you'd better build your stuff under ~/src it is recommended linux way. > Does the current method of packaging up the kernel sources / sending > them as debian packages / kernel source tarballs help anyone? It doesn't > seem to do me any good; but perhaps there are better ways of working > with the sources & debian kernel patches? > > If I want to build my own kernel from the debian sources, I apt-get > source the appropriate kernel-image package, run debuild and grab the > appropriate dir once it's all be setup. (usually 686-smp or k7). > > Then I rename that, do the normal: > make menuconfig; make; make modules; make modules_install;make install man make-kpkg > Then there doesn't seem to be a simple way to make the initrd so I > always have to manually run: > mkinitrd -o /boot/initrd.img-(VERSION) (VERSION) the debian way is to a create a package that places the file to their destination, it has also an initrd switch. yes i know it's not perfect and omits sometimes very strange messages, but it's a first step. i'd suggest you google for "debian kernel howto" for the next time! have fun. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
