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, 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. Whi
Hmm, interestingly only swap and tmp were listed with an UUID. But alas,
it did not work out to list the other partitions with their UUID.
Should I mention that software raid and lvm is used?
KR, m
On Mon, 2011-02-28 at 16:57 +0200, Andrei Popescu wrote:
> On Lu, 28 feb 11, 15:54:38, dirkyd
It's grub2 and UUIDs are used; and grub finds the kernel and the ramdisc
file. (If it would not find them, grub would show a different msg.
Already encountered and solved that a while ago when grub had an issue
with wanting "/boot" in the path ;)
I suspect the script that generates the ramdisc to
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
Hi all,
after updating my Debian box, it ceases to boot with above error. I use kernel
2.6.32. Booting older 2.6.28 seems to run the init process well (but has other
issues).
Somebody has an idea what went wrong?
KR, m
--
NEU: FreePhone - kostenlos mobil telefonieren und surfen!
6 matches
Mail list logo
