From: Matthew Gillen <me@mattgillen.net>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] linux kernel 2.6.39 LVM2 rootfs initrd kernel panic "no rootfs found" with userspace dmsetup+libdevmapper <= 1.02.48
Date: Mon, 08 Aug 2011 09:39:17 -0400 [thread overview]
Message-ID: <4E3FE705.8040600@mattgillen.net> (raw)
In-Reply-To: <CAPweEDyrD2VE4DQ6rp=rfJ-MGa_rz4=c3-_+FVNMf3MHhAQZVA@mail.gmail.com>
On 08/06/2011 06:09 PM, Luke Kenneth Casson Leighton wrote:
> so at this point i'm puzzled, because it's userspace-kernelspace
> interaction and yet there's no recognition of this inter-dependency in
> the debian package specs...
>
> so, we have an unusual situation in which the linux kernel appears to
> require a dependency on a specific version of a userspace library for
> booting a system (which the debian linux kernel maintainer quite
> rightly objected to "fixing" by adding random dependencies for random
> userspace libraries. as they said in Galaxy Quest, "ohhh. that's not
> riiiight"...)
>
> so, with that as background, one debian user raised an interesting
> question: has any _other_ gnu/linux distro encountered this issue, and
> if so, how was it resolved?
I don't think it is resolved anywhere (Redhat/Fedora kernel packages
also have a very minimal set of user-space deps that do not include any
of the LVM auxiliary programs. It's a nasty problem that would only
really be solved by packaging kernel-modules (or least the ones with
additional user-space dependencies) separately from the kernel core.
But package maintainers are resistant to that because it makes for more
management headaches...
The RPMFusion/kmod packages for Fedora take this approach for various
third-party modules (e.g. the linkage between the nvidia kernel module
and the nvidia libGL userspace library; separate packages because the
kernel module is tied to both a kernel version and a driver-release
version, while the userspace library is tied only to a driver-release
version). I'm sure if you trolled the fedora-devel list from a few
years ago you'd find a big debate about this (there was at one time a
question as to whether the kmod packaging system would be used for
officially supported modules; they decided to not support kmod officially).
Matt
prev parent reply other threads:[~2011-08-08 13:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 22:09 [linux-lvm] linux kernel 2.6.39 LVM2 rootfs initrd kernel panic "no rootfs found" with userspace dmsetup+libdevmapper <= 1.02.48 Luke Kenneth Casson Leighton
2011-08-08 13:39 ` Matthew Gillen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E3FE705.8040600@mattgillen.net \
--to=me@mattgillen.net \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).