ich habe probleme beim installieren eines selbst gebackenen kernels (version 2.4.22) nach debian art. das kompilieren geht zwar, doch beim installieren erscheint eine warnung (sorry für den langen post):
Code: Alles auswählen
mwadishi:/usr/src# dpkg -i kernel-image-2.4.22_10.00.Custom_i386.deb
(Reading database ... 77941 files and directories currently installed.)
Preparing to replace kernel-image-2.4.22 10.00.Custom (using kernel-image-2.4.22_10.00.Custom_i386.deb) ...
You are attempting to install a kernel image (version 2.4.22)
However, the directory /lib/modules/2.4.22 still exists. If this
directory belongs to a previous kernel-image-2.4.22 package, and if
you have deselected some modules, or installed standalone modules
packages, this could be bad. However, if this directory exists because
you are also installing some stand alone modules right now, and they
got unpacked before I did, then this is pretty benign. Unfortunately,
I can't tell the difference.
If /lib/modules/2.4.22 belongs to a old install of
kenel-image-2.4.22, then this is your last chance to abort the
installation of this kernel image (nothing has been changed yet).
If this directory is because of stand alone modules being installed
right now, or if it does belong to an older kernel-image-2.4.22
package but you know what you are doing, and if you feel that this
image should be installed despite this anomaly, Please answer n to the
question.
Otherwise, I suggest you move /lib/modules/2.4.22 out of the way,
perhaps to /lib/modules/2.4.22.old or something, and then try
re-installing this image.
Do you want to stop now? [Y/n]nCode: Alles auswählen
Unpacking replacement kernel-image-2.4.22 ...
Setting up kernel-image-2.4.22 (10.00.Custom) ...
Not updating image symbolic links since we are being updated (10.00.Custom)
A new kernel image has been installed, and usually that means
that some action has to be taken to make sure that the new
kernel image is used next time the machine boots. Usually,
this entails running a ``bootloader'' like SILO, loadlin, LILO,
ELILO, QUIK, VMELILO, ZIPL, or booting from a floppy. (Some
boot loader, like grub, for example, do not need to be run on
each new image install, so please ignore this if you are using
such a boot loader).
A new kernel image has been installed at /boot/vmlinuz-2.4.22
(Size: 1758kB)
Symbolic links, unless otherwise specified, can be found in /
LILO sets up your system to boot Linux directly from your hard
disk, without the need for booting from a boot floppy.
WARNING
If you are keeping another operating system or another version
of Linux on a separate disk partition, you should not have LILO
install a boot block now. Wait until you read the LILO documentation.
That is because installing a boot block now might make the other
system un-bootable. If you only want to run this version of Linux,
go ahead and install the boot block here. If it does not work, you
can still boot this system from a boot floppy.
Would you like to create a boot floppy now? [No]
You already have a LILO configuration in /etc/lilo.conf
Install a boot block using the existing /etc/lilo.conf? [Yes]
Testing lilo.conf ...
Testing successful.
Installing the partition boot sector...
Installation successful.
mwadishi:/usr/src# danke für eine antwort....
gruss, hupf
