DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello,
can someone help me.
I can't update the new image-2.6.26-1-686_2.6.26-13lenny2
with security update
E: /var/cache/apt/archives/linux-
image-2.6.26-1-686_2.6.26-13lenny2_i386.deb: fehlgeschlagen in buffer_write(fd) (10, ret=-1)
or with aptitude
Vorkonfiguration der Pakete ...
(Lese Datenbank ... 126387 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereiten zum Ersetzen von linux-image-2.6.26-1-686 2.6.26-13 (durch .../linux-image-2.6.26-1-686_2.6.26-13lenny2_i386.deb) ...
The directory /lib/modules/2.6.26-1-686 still exists. Continuing as directed.
Done.
Entpacke Ersatz für linux-image-2.6.26-1-686 ...
dpkg: Fehler beim Bearbeiten von /var/cache/apt/archives/linux-image-2.6.26-1-686_2.6.26-13lenny2_i386.deb (--unpack):
fehlgeschlagen in buffer_write(fd) (10, ret=-1): Backend dpkg-deb während »./lib/modules/2.6.26-1-686/kernel/drivers/hwmon/dme1737.ko«: Auf dem Gerät ist kein Speicherplatz mehr verfügbar
dpkg-deb: Unterprozess paste mit Signal (Datenübergabe unterbrochen (broken pipe)) getötet
Running postrm hook script /sbin/update-grub.
Searching for GRUB installation directory ... found: /boot/grub
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-2.6.26-1-686
Found kernel: /boot/vmlinuz-2.6.18-6-686
Found kernel: /boot/vmlinuz-2.6.18-4-686
Updating /boot/grub/menu.lst ... done
Last edited by Stephan789; 04-29-2009 at 02:29 PM.
Much Thanks!
I have differnt partions for all. There is space on disk but I think not in the parition for the image. I don't know but I think there are old Images. Is it possible to delete them and how?
Last edited by Stephan789; 05-05-2009 at 10:27 AM.
Hmm hard to tell what's going on from those screenshots.. it looks like / is full but you have som many other partitions, I don't understand why / would have that much data in it..
could you post the output of the following command here ?
Thanks! I have got the answer. I have removed with aptitude the kernel 2.6.18-6-686 and 2.6.18-4-686
Now I have enough disk space. Than I have installed
linux-image 2.6.26-libre2-1-686 because I thought that libre use a little less disk space. What do you think is libre stabil?
yes the libre kernel would likely be smaller. and if you don't run into any issues with devices not working due to missing firmware, you should be good to go.
From what I can see it looks like the libre kernel has all the non-free binary firmware blobs removed from it. Debian is working towards this in their mainline kernels, but it's a slow process.
When you uninstalled those kernels did you also go through your system looking for any old initrd.img or vmlinuz files sitting in /boot that you no longer need ? and did you check /usr/src for header files left over from the kernel versions you removed ?
I always do a manual check since purging the old kernels doesn't necessarily remove everything.
The old initrd.img or vmlinuz files was remove by aptitude. I have also delete one bak file with mc.
I think I have no problems with missing firmware.
It is all very well.
Thanks a lot!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.