Re: kernel upgrade problem
On 12/31/06 06:40:52PM -0600, Russ Cook wrote: > I had already checked with 'df' before posting, but I attach the > results in case it offers a clue. > > Thanks for the reply, > Russ > Script started on Sun 31 Dec 2006 06:38:39 PM CST > Filesystem 1K-blocks Used Available Use% Mounted on > /dev/hda1 255912200418 41841 83% / > tmpfs 1674944 0 1674944 0% /lib/init/rw > udev 1024064 10176 1% /dev > tmpfs 1674944 0 1674944 0% /dev/shm > /dev/hda9181745360 90136804 82376404 53% /home > /dev/hda8 369000 8355340985 3% /tmp > /dev/hda5 4807056 2657124 1905748 59% /usr > /dev/hda6 2885780 1257440 1481752 46% /var > > Script done on Sun 31 Dec 2006 06:38:39 PM CST Did you check the inode count? If not, see what 'df -i' says. Jim. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel upgrade problem
Manolo Díaz wrote: Russ Cook escribió: I'm running a dual core amd64 with Debian unstable, kernel 2.6.17-2-amd64. Today, I tried to upgrade to kernel 2.6.18-3-amd64. I get an unexpected error message concerning a buffer-write failure. I have attached a script file with the error message. I searched the mailing list, and didn't see a related post. I apologize in advance if I missed it. Can anyone shed some light? Thanks, Russ Script started on Sun 31 Dec 2006 12:59:28 PM CST (Reading database ... 121478 files and directories currently installed.) Unpacking linux-image-2.6.18-3-amd64 (from .../linux-image-2.6.18-3-amd64_2.6.18-8_amd64.deb) ... Done. dpkg: error processing /var/cache/apt/archives/linux-image-2.6.18-3-amd64_2.6.18-8_amd64.deb (--install): failed in buffer_write(fd) (9, ret=-1): backend dpkg-deb during `./lib/modules/2.6.18-3-amd64/kernel/fs/cifs/cifs.ko': No space left on device That's your clue: No space left on device. What does df command say? dpkg-deb: subprocess paste killed by signal (Broken pipe) Running postrm hook script /usr/sbin/update-grub. Searching for GRUB installation directory ... found: /boot/grub 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.17-2-amd64 Found kernel: /boot/vmlinuz-2.6.16-2-amd64-k8-smp Updating /boot/grub/menu.lst ... done Errors were encountered while processing: /var/cache/apt/archives/linux-image-2.6.18-3-amd64_2.6.18-8_amd64.deb Script done on Sun 31 Dec 2006 12:59:38 PM CST I had already checked with 'df' before posting, but I attach the results in case it offers a clue. Thanks for the reply, Russ Script started on Sun 31 Dec 2006 06:38:39 PM CST Filesystem 1K-blocks Used Available Use% Mounted on /dev/hda1 255912200418 41841 83% / tmpfs 1674944 0 1674944 0% /lib/init/rw udev 1024064 10176 1% /dev tmpfs 1674944 0 1674944 0% /dev/shm /dev/hda9181745360 90136804 82376404 53% /home /dev/hda8 369000 8355340985 3% /tmp /dev/hda5 4807056 2657124 1905748 59% /usr /dev/hda6 2885780 1257440 1481752 46% /var Script done on Sun 31 Dec 2006 06:38:39 PM CST
Re: kernel upgrade problem
Am Sonntag, 31. Dezember 2006 20:56 schrieb Russ Cook: > dpkg: error processing > during `./lib/modules/2.6.18-3-amd64/kernel/fs/cifs/cifs.ko': > No space left on device Your disk (probably /boot ) is full :-) Best regards -- Udo Burghardt http://UdoBurghardt.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel upgrade problem
Russ Cook escribió: > I'm running a dual core amd64 with Debian unstable, kernel > 2.6.17-2-amd64. > Today, I tried to upgrade to kernel 2.6.18-3-amd64. I get an unexpected > error message concerning a buffer-write failure. I have attached a > script file with the error message. I searched the mailing list, and > didn't > see a related post. I apologize in advance if I missed it. Can anyone > shed some light? > Thanks, > Russ > > > Script started on Sun 31 Dec 2006 12:59:28 PM CST > (Reading database ... 121478 files and directories currently installed.) > Unpacking linux-image-2.6.18-3-amd64 (from > .../linux-image-2.6.18-3-amd64_2.6.18-8_amd64.deb) ... > Done. > dpkg: error processing > /var/cache/apt/archives/linux-image-2.6.18-3-amd64_2.6.18-8_amd64.deb > (--install): > failed in buffer_write(fd) (9, ret=-1): backend dpkg-deb during > `./lib/modules/2.6.18-3-amd64/kernel/fs/cifs/cifs.ko': No space left on device > That's your clue: No space left on device. What does df command say? > dpkg-deb: subprocess paste killed by signal (Broken pipe) > Running postrm hook script /usr/sbin/update-grub. > Searching for GRUB installation directory ... found: /boot/grub > 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.17-2-amd64 > Found kernel: /boot/vmlinuz-2.6.16-2-amd64-k8-smp > Updating /boot/grub/menu.lst ... done > > Errors were encountered while processing: > /var/cache/apt/archives/linux-image-2.6.18-3-amd64_2.6.18-8_amd64.deb > > Script done on Sun 31 Dec 2006 12:59:38 PM CST > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel upgrade problem
Russ Cook escribió: > I'm running a dual core amd64 with Debian unstable, kernel > 2.6.17-2-amd64. > Today, I tried to upgrade to kernel 2.6.18-3-amd64. I get an unexpected > error message concerning a buffer-write failure. I have attached a > script file with the error message. I searched the mailing list, and > didn't > see a related post. I apologize in advance if I missed it. Can anyone > shed some light? > Thanks, > Russ > > > Script started on Sun 31 Dec 2006 12:59:28 PM CST > (Reading database ... 121478 files and directories currently installed.) > Unpacking linux-image-2.6.18-3-amd64 (from > .../linux-image-2.6.18-3-amd64_2.6.18-8_amd64.deb) ... > Done. > dpkg: error processing > /var/cache/apt/archives/linux-image-2.6.18-3-amd64_2.6.18-8_amd64.deb > (--install): > failed in buffer_write(fd) (9, ret=-1): backend dpkg-deb during > `./lib/modules/2.6.18-3-amd64/kernel/fs/cifs/cifs.ko': No space left on device > That's your clue: No space left on device. What does df command say? > dpkg-deb: subprocess paste killed by signal (Broken pipe) > Running postrm hook script /usr/sbin/update-grub. > Searching for GRUB installation directory ... found: /boot/grub > 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.17-2-amd64 > Found kernel: /boot/vmlinuz-2.6.16-2-amd64-k8-smp > Updating /boot/grub/menu.lst ... done > > Errors were encountered while processing: > /var/cache/apt/archives/linux-image-2.6.18-3-amd64_2.6.18-8_amd64.deb > > Script done on Sun 31 Dec 2006 12:59:38 PM CST > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: when is etch safe to access internet?
On Sun December 31 2006 11:45, Douglas Tutty wrote: > Hi, > > Two interrelated questions: > > Short question: when can my Etch amd64 box access the net via dialup > safely? At one point recently in relation to Etch (pre RC1), there was > mention somewhre (perhaps the relase notes of the time) [sorry for my > spottty memory] that a testing box should not be connected directly to > the internet. I can't find that anymore. Right now I'm connected via > an old 486 with a failing NIC. Now that Etch is frozen, is it safe to > connect directly with the modem? I have not heard/read that before. Personally I wouldn't be more concerned about connecting a computer to the net with a modem or nic. Mind what you've read though, I probably wouldn't even notice a security announcement re: modems. > Long question: How is security and etch transition from testing to > stable handled? The release and security pages say that the testing > distribution does not get security updates. Does this mean that Etch > must wait to be 'stable' before security is addressed or is it just a > hand-off from the individual maintainers to the security team? This > could suggest that there will be some security holes between the time it > is released and when security updates are produced. The security team does release security updates for testing when needed, I run etch and I do have s.d.o in my sources.list. > I guess everyone is getting itchy for etch (etchy?). I'm etchy already, and loving it.. :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: when is etch safe to access internet?
On Sun, Dec 31, 2006 at 02:45:57PM -0500, Douglas Tutty wrote: > Hi, > > Two interrelated questions: > > Short question: when can my Etch amd64 box access the net via dialup > safely? At one point recently in relation to Etch (pre RC1), there was > mention somewhre (perhaps the relase notes of the time) [sorry for my > spottty memory] that a testing box should not be connected directly to > the internet. I can't find that anymore. Right now I'm connected via > an old 486 with a failing NIC. Now that Etch is frozen, is it safe to > connect directly with the modem? > The answer is yes. The recommendation to not directly connect an Etch or Sid box to the 'net is given so that people will not blindly go about connecting to the 'net and thinking that they are perfectly safe. Now, it is probably safer to connect a Sid box (packages take from 2 to 10 days to migrate from unstable to testing, even for security fixes). However, given that Etch is frozen, it is receiving a great deal of attention. > Long question: How is security and etch transition from testing to > stable handled? The release and security pages say that the testing > distribution does not get security updates. Does this mean that Etch > must wait to be 'stable' before security is addressed or is it just a > hand-off from the individual maintainers to the security team? This > could suggest that there will be some security holes between the time it > is released and when security updates are produced. > Security support for a release is genereally "officially" announced in the pre-release freeze period. That way, when the release "happens" the security support is already up and running. There is a team of DDs who have a project going called "testing security", IIRC, which is supposed to bring the same level of security support to testing as exists with stable. > I guess everyone is getting itchy for etch (etchy?). > Personally, I can't wait, but there are still some serious transitional bugs to work out. Regards, -Roberto -- Roberto C. Sanchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
kernel upgrade problem
I'm running a dual core amd64 with Debian unstable, kernel 2.6.17-2-amd64. Today, I tried to upgrade to kernel 2.6.18-3-amd64. I get an unexpected error message concerning a buffer-write failure. I have attached a script file with the error message. I searched the mailing list, and didn't see a related post. I apologize in advance if I missed it. Can anyone shed some light? Thanks, Russ Script started on Sun 31 Dec 2006 12:59:28 PM CST (Reading database ... 121478 files and directories currently installed.) Unpacking linux-image-2.6.18-3-amd64 (from .../linux-image-2.6.18-3-amd64_2.6.18-8_amd64.deb) ... Done. dpkg: error processing /var/cache/apt/archives/linux-image-2.6.18-3-amd64_2.6.18-8_amd64.deb (--install): failed in buffer_write(fd) (9, ret=-1): backend dpkg-deb during `./lib/modules/2.6.18-3-amd64/kernel/fs/cifs/cifs.ko': No space left on device dpkg-deb: subprocess paste killed by signal (Broken pipe) Running postrm hook script /usr/sbin/update-grub. Searching for GRUB installation directory ... found: /boot/grub 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.17-2-amd64 Found kernel: /boot/vmlinuz-2.6.16-2-amd64-k8-smp Updating /boot/grub/menu.lst ... done Errors were encountered while processing: /var/cache/apt/archives/linux-image-2.6.18-3-amd64_2.6.18-8_amd64.deb Script done on Sun 31 Dec 2006 12:59:38 PM CST
when is etch safe to access internet?
Hi, Two interrelated questions: Short question: when can my Etch amd64 box access the net via dialup safely? At one point recently in relation to Etch (pre RC1), there was mention somewhre (perhaps the relase notes of the time) [sorry for my spottty memory] that a testing box should not be connected directly to the internet. I can't find that anymore. Right now I'm connected via an old 486 with a failing NIC. Now that Etch is frozen, is it safe to connect directly with the modem? Long question: How is security and etch transition from testing to stable handled? The release and security pages say that the testing distribution does not get security updates. Does this mean that Etch must wait to be 'stable' before security is addressed or is it just a hand-off from the individual maintainers to the security team? This could suggest that there will be some security holes between the time it is released and when security updates are produced. I guess everyone is getting itchy for etch (etchy?). Thanks, Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Réponse automatique
This email is CLOSED. Please remove of your desk. cette adresse email n'est plus d'actualité, merci de nous supprimer de vos fichiers.
