Hi, About question 2: >>"Jon" == <[EMAIL PROTECTED]> writes:
Jon> 2) I am use to directly building slackware kernals. Will Jon> something like make config; make; make zImage; make zlilo; make Jon> modules; make modules_install break any dependancy info? I Jon> noticed make-kpkg; what options would be comparable to the makes Jon> above? The procedure would work, but leave no record with dpkg about the kernel being used. I like being able to use dpkg to track kernel images/sources and easy install/de-install. The above sequence is equivalent to the excerpt from the README file: INSTALLATION NOTES: For the Brave and the impatient: 1% cd <kernel source tree> 2% make config # or make menuconfig or make xconfig and configure 3% make-kpkg -r=custom.1.0 kernel_image 4% dpkg -i ../kernel-image-X.XXX_1.0_<arch>.deb 5% shutdown -r now # If and only if LILO worked or you have a means of # booting the new kernel. YOU HAVE BEEN WARNED!! Detailed instructions ... manoj -- "There is no law that vulgarity and literary excellence cannot coexist." Trevor Hodge Manoj Srivastava <url:mailto:[EMAIL PROTECTED]> Mobile, Alabama USA <url:http://www.datasync.com/%7Esrivasta/> -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]