On 2009-11-20 17:33 +0100, drz wrote:
...
>This happens when update-initramfs tries to compress the initramfs.
>I.e. the device where no space is left is /boot.
>
>> /dev/hda2 93M 69M 20M 78% /boot
>
>That may be a bit small these days with the default update-initramfs
>configura
Hi,
How many kernel images are installed to take 69MB in the /boot?
Regards,
2009/11/20 Sven Joachim
> On 2009-11-20 17:33 +0100, drz wrote:
>
> > Im facing a problem with aptitude (running testing).
> >
> > If I run:
> > # aptitude update
> > E: dpkg was interrupted, you must manually run 'dp
On 2009-11-20 17:33 +0100, drz wrote:
> Im facing a problem with aptitude (running testing).
>
> If I run:
> # aptitude update
> E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to
> correct
> the problem.
> Couldnt lock Cache-File ... (translation by me)
> Then download in
On Friday November 20 2009 9:33:41 am drz wrote:
> gzip: stdout: No space left on device
> update-initramfs: failed for /boot/initrd.img-2.6.30-2-powerpc
> dpkg: Unterprozess installiertes post-installation-Skript gab den
> Fehlerwert 1 zurück
>
> No space left on device? Which device and how can
Hello
Im facing a problem with aptitude (running testing).
If I run:
# aptitude update
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct
the problem.
Couldnt lock Cache-File ... (translation by me)
Then download info and:
E: dpkg was interrupted, you must manually
5 matches
Mail list logo
