Manoj Srivastava declaimed:
> Hmm. I think I know what is going on here, but just to make
> sure I am not totally off base here: You have instructed your boot
> loader to expect an initrd kernel (and that is required to load the
> newer official kernel images), and were trying to build an
>>"Paul" == Paul Mackinney <[EMAIL PROTECTED]> writes:
Paul> I've successfully installed several kernel's in the past using your
Paul> (excellent) README file, but I've just spent 3 days unsuccessfully
Paul> trying to boot from a newly compiled kernel package. Turns out that I
Paul> had to ad
Manoj Srivastava declaimed:
> This was a bug. The check I had in the image postinst was
> being too rigorous, and always failed. kernel-package from the last
> day or so should have this fixed.
>
> manoj
Manoj,
I've successfully installed several kernel's in the past using your
(ex
>>"Shaul" == Shaul Karl <[EMAIL PROTECTED]> writes:
Shaul> Next I installed kernel-image-2.2.20_custom.2.0_i386.deb and got both
Shaul> vmlinuz and vmlinuz.old pointing to /boot/vmlinuz-2.2.20. Yet
Shaul> /usr/share/doc/kernel-package/README.gz states that
Shaul> Normally, that is only
On Fri, Jan 04, 2002 at 06:48:36PM +0200, Shaul Karl wrote:
| kernel-package is not behaving the way I expected it with regard to
| moving the old vmlinuz to vmlinuz.old.
| Can you help identifying what am I doing wrong?
|
| The point is that I had
| /vmlinuz -> /boot/vmlinuz-2.2.20 and
|
kernel-package is not behaving the way I expected it with regard to
moving the old vmlinuz to vmlinuz.old.
Can you help identifying what am I doing wrong?
The point is that I had
/vmlinuz -> /boot/vmlinuz-2.2.20 and
/vmlinuz.old -> /boot/vmlinuz-2.2.19pre17,
where the 2.2.20 was instal
6 matches
Mail list logo
