Re: A few questions.
About question 2:
>>"Jon" == <firstname.lastname@example.org> 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
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
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!!
"There is no law that vulgarity and literary excellence cannot
coexist." Trevor Hodge
Manoj Srivastava <url:mailto:email@example.com>
Mobile, Alabama USA <url:http://www.datasync.com/%7Esrivasta/>
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com