On 28 Jun 2001 at 21:51 (-0700), Ben Ford wrote:
| Brent Verner wrote:
|
| >On 27 Jun 2001 at 21:04 (-0400), M. Jackson Wilkinson wrote:
| >|
| >| Does anyone have a working kernel-image-2.4.5 package based off of the
| >| kernel-image-2.4.2 .config file? Would you be willing to share it with
| >me? | I am having a few problems, and I've noticed that there are patches
| >in
| >| kernels > 2.4.2.
| >
| >it /appears/ that kernel 2.4.5 require a newer version of modutils,
| >which depends on a newer dpkg version, than progeny distributes.
| >
|
| Build a monolithic kernel. It has the advantage of being marginally
| faster, while only wasting a few k of memory.
yes, that would be the normal thing, I'd do. In fact, I'd not even
use make-kpkg at all, but I'm trying to build a kernel image
that'll be used on a number of differently configured systems. I
originally tried to use a vanilla kernel from kernel.org, but
selecting (most) all drivers left me with an unbootable kernel, so
I decided I'd use the kernel-source from unstable, since surely
it was a known working config. It is, but the initrd image made
by the unstable make-kpkg uses mkinitrd instead of update-initrd
to create an initrd image that has /all/ modules on the image.
The end effect of this is that building the kernel-source from
unstable on a progeny box will build an initrd image with a kernel
that has almost no drivers compiled statically, including the
ide-disk driver, which I must have at initrd time to mount /.
I've reconfigured the unstable kernel-source to have a static
ide-disk driver, so I'm working now.
The moral of the story is that the kernel-source/config from
unstable can be used, but make sure that you reconfigure to
build the unix.o and whatever driver your / device needs into
the kernel (not as a module).
thanks for reading :-)
b
--
- - - - - -=( d a m o n b r e n t v e r n e r )=- - - - - - -
c e r t i f i e d n o s o u r c o p h o b i c
