Am 30.04.2014 01:20, schrieb Elimar Riesebieter: > * Elimar Riesebieter <riesebie@lxtec.de> [2014-04-30 00:50 +0200]: > >> * Thore <thore@datensumpf.de> [2014-04-30 00:29 +0200]: >> >> [...] >>> ls -lah /boot/ >>> total 4.9M >>> drwxr-xr-x 2 root root 4.0K Apr 26 21:37 . >>> drwxr-xr-x 25 root root 4.0K Feb 3 16:53 .. >>> -rw-r--r-- 1 root root 2.1M Apr 23 06:04 System.map-3.2.0-4-amd64 >>> -rw-r--r-- 1 root root 127K Apr 23 06:04 config-3.2.0-4-amd64 >>> -rw-r--r-- 1 root root 2.8M Apr 23 06:01 vmlinuz-3.2.0-4-amd64 >>> >>> >>> lrwxrwxrwx 1 root root 30 Nov 26 2012 initrd.img -> >>> /boot/initrd.img-3.2.0-4-amd64 >> >> Es existiert wohl offensichtlich kein /boot/initrd.img-3.2.0-4-amd64? > > update-initramfs(8) > > Versuche als root: > # update-initramfs -u > > Elimar > update-initramfs -u /boot/initrd.img-3.2.0-4-amd64 does not exist. Cannot update. Nur was tut man dagegen?
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature