On Tue, Feb 20, 2007 at 12:01:20PM +0100, maximilian attems wrote:
> copy_exec() explicitly copies the non-optimized libraries,
> don't know yet why /lib/libgcc_s.so.1 falls into that category.
> so that looks more like an possible initramfs-tools bug.
>
> the intersting output is
> ldd /usr/sbin/
reassign 411284 initramfs-tools
severity 411284 minor
stop
On Tue, 20 Feb 2007, David Härdeman wrote:
> reassign 411284 evms
> thanks
>
> On Mon, Feb 19, 2007 at 11:15:20PM +0200, Sami Liedes wrote:
> >On Mon, Feb 19, 2007 at 09:38:58PM +0100, David Härdeman wrote:
> >>First of all, the 'Volume
On Tue, Feb 20, 2007 at 12:13:07AM +0100, David Härdeman wrote:
> >Ok. Then there's left the error produced by evms_activate after doing
> >what it needed to do ("libgcc_s.so.1 must be installed for
> >pthread_cancel to work\nAborted") which I mentioned in my original
> >report, perhaps that's some
reassign 411284 evms
thanks
On Mon, Feb 19, 2007 at 11:15:20PM +0200, Sami Liedes wrote:
On Mon, Feb 19, 2007 at 09:38:58PM +0100, David Härdeman wrote:
First of all, the 'Volume group "root" not found' warning is harmless.
The reason that you see it is that your luks volume is called
"root-cr
On Mon, Feb 19, 2007 at 09:38:58PM +0100, David Härdeman wrote:
> First of all, the 'Volume group "root" not found' warning is harmless.
> The reason that you see it is that your luks volume is called
> "root-crypted", which corresponds to /dev/mapper/root-crypted which
> is the same device name
Sami Liedes wrote:
I don't know what causes the message about vg "root" to not be found.
I have no such vg, although it might be that I have have once had
such.
First of all, the 'Volume group "root" not found' warning is harmless.
The reason that you see it is that your luks volume is called
severity 411284 wishlist
reassign 411284 cryptsetup
stop
On Sat, 17 Feb 2007, Sami Liedes wrote:
> The created initramfs for some reason seems to fail to activate evms.
>
> I have a setup where I have evms+lvm2, and an evms-volume
> "root-crypted" is a luks volume of the root file system.
the e
Package: initramfs-tools
Version: 0.85e
Severity: normal
The created initramfs for some reason seems to fail to activate evms.
I have a setup where I have evms+lvm2, and an evms-volume
"root-crypted" is a luks volume of the root file system.
This is what happens (typed, not captured from serial
8 matches
Mail list logo