On Thu, May 14, 2009 at 10:20 AM, Jeff Mahoney <jeffm(a)suse.com> wrote:
In the first case, they're harmless.
ok, good to know. i might simply suggest that "FATAL" fails to
communicate "harmless" ...
It's an unfortunate side effect of
having the kernel split into multiple packages.
just to understand, what changed to start generating these messages?
is it just the splitting that's new? or perhaps an artifact of 'new'
kernel-$flavor-extra depends on kernel-$flavor which
depends on kernel-$flavor-base. At each
dependency, it's not guaranteed that the next package will be installed
so we need to attempt to build the initrd then. Sometimes the
dependencies won't be met until the next package is installed.
Ultimately, the correct initrd is generated - it's just noisy in the
that's clear. thanks.
I'd recommend opening a bug report against
perl-bootloader for the other issues.
already done for some parsing issues. fixed, but not released -- yet.
how about the,
2009-05-14 09:41:39 WARNING: Tools::GetMultipath: multipath command
failed with 256
2009-05-14 09:41:39 WARNING: Core::GetExtendedPartition: Specified device
/dev/md0 is not valid and cannot be used as
base for detecting an
extended partition on the same disk.
messages? are _these_ perl-bootloader-related ? i wasn't clear what
you meant by 'other issues' ...
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org