Re: make-kpgk modules troubles
Hi Thomas -- A while ago you asked: Until recently, I just rolled my own kernel as I was used to do with Slackware. But since I found out about make-kpkg, I decided to do things the Debian way and use that instead. After much hassle wit the broken tar (solved by downgrading), there's still a problem: Whenever I try to make a modules package for my system, I end up with a message like Modules not configured, so not making modules. Then Joey Hess replied: Sorry, I can't help you with your problem, but this does raise a question in my mind: what exactly is the benefit of using the kernel-package vs. rolling your own kernel? The following might be useful input for both questions: make-kpkg provides a kernel-image package that can be managed and manipulated like other Debian packages. The accessibility of all the files involved in upgrading a kernel to the Debian tools is an advantage, especially if one is trying out many kernel configurations and/or versions. Once I run make-kpkg kernel_image it is very easy to make a new copy of the Debian boot disk, using the boot-floppies package: cd /usr/src/bootfloppies-1.1.1 ./bootdisk.sh kernel-image-2.0.whatever.deb /dev/fd0 1440 This makes a handy emergency boot disk (even though its initial primary design was for installation.) One can't use the boot floppies script without the kernel-image .deb file. HTH, Susan Kleinmann -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: make-kpgk modules troubles
Wouldn't it be more appropriate to offer the user the option of inserting a floppy and making a boot disk as part of the make-kpkg kernel_image? Or perhaps the ./bootdisk.sh kernel-images NOT to require the .deb format? I must admit I haven't given this a lot of thought. But I too was weaned on Slackware and am used to rolling my own. Jeff The following might be useful input for both questions: make-kpkg provides a kernel-image package that can be managed and manipulated like other Debian packages. The accessibility of all the files involved in upgrading a kernel to the Debian tools is an advantage, especially if one is trying out many kernel configurations and/or versions. Once I run make-kpkg kernel_image it is very easy to make a new copy of the Debian boot disk, using the boot-floppies package: cd /usr/src/bootfloppies-1.1.1 ./bootdisk.sh kernel-image-2.0.whatever.deb /dev/fd0 1440 This makes a handy emergency boot disk (even though its initial primary design was for installation.) One can't use the boot floppies script without the kernel-image .deb file. HTH, Susan Kleinmann -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: make-kpgk modules troubles
On Wed, 11 Sep 1996, Thomas Baetzler wrote:
Until recently, I just rolled my own kernel as I was used to do
with Slackware. But since I found out about make-kpkg, I decided
to do things the Debian way and use that instead. After much hassle
wit the broken tar (solved by downgrading), there's still a problem:
Whenever I try to make a modules package for my system, I end up
with a message like Modules not configured, so not making modules.
Sorry, I can't help you with your problem, but this does raise a question
in my mind: what exactly is the benefit of using the kernel-package vs.
rolling your own kernel? When I build my kernel, I have to build it 3
times, for a 586, 468, and a pentium. The 586 and 486 are diskless
clients, and all of them need different things in the kernel that
can't be provided as modules (math emulation for the 586, built in
nfs-root for the diskless machines, etc). So I've written scripts
to automate building and distributing the kernel to the 3 computers.
How would using kernel-package help me? I just don't see much of a point
to it for someone who's already comfortable with building the kernel,
unless you need to make a single kernel package to be used on a bunch of
machines.
--
#!/usr/bin/perl -i=-/*/~%*~%/~~%/~~~-/*/_/=~~~-/~~! # [EMAIL PROTECTED]
$o=35;$_=$^I-*!=_!/;s/~/!*/g;s~%~-/ / ~g;$_.='--- Joey Hess
';s/=/__/g;y|*!| \\|;for(split/-/){print' 'x$o--.$_\n}# a M.C. Escher fan
How appropriate, you fight like a cow. - - Guybrush Threepwood
