On Mon, 2011-02-28 at 17:13 +, Wolodja Wentland wrote:
> A quick look at the manpage reveals that you have to specify one of the
> supported commands. Let's try "list":
>
> $ apt-listbugs list apt/0.8.11.5
> serious bugs of apt (0.8.11.5 -> 0.8.11.5)
> #558784 - apt: re-adds removed keys
> S
On Mon, Feb 28, 2011 at 16:40 +0100, dirkydirk wrote:
> On Mon, 2011-02-28 at 15:17 +, Wolodja Wentland wrote:
> > On Mon, Feb 28, 2011 at 15:37 +0100, dirkydirk wrote:
> > Which version of libc-bin do you have installed (dpkg -l libc-bin). If you
> > have 2.11.2-12 you might have run into
[..
On Mon, 2011-02-28 at 15:17 +, Wolodja Wentland wrote:
> On Mon, Feb 28, 2011 at 15:37 +0100, dirkydirk wrote:
>
> > I conclude then, there's an issue with the update script. (I'm running
> > Debian sid, btw.)
>
> An important piece of information. Which version of libc-bin do you have
> inst
On Mon, Feb 28, 2011 at 15:37 +0100, dirkydirk wrote:
> I conclude then, there's an issue with the update script. (I'm running
> Debian sid, btw.)
An important piece of information. Which version of libc-bin do you have
installed (dpkg -l libc-bin). If you have 2.11.2-12 you might have run into
[
Hi,
yes, there's init in it. But the directory structure of the ramdisc
looks quite different from a 2.6.31 ramdisc on another computer.
Unfortunately I did run update-initramfs -k all, and now even the 2.6.26
kernel refuses to boot. Same error.
>From the recent grml live-distro I copied kernel
5 matches
Mail list logo
