Re: help with lvm2/devmapper (or orphaning)?
On Tue, 23 Mar 2004 17:00:26 +0000, Miquel van Smoorenburg wrote:
> In article <[🔎] 1080060532.29944.19.camel@wax.hq.voxel.net>,
> Andres Salomon <dilinger@voxel.net> wrote:
>>I've been neglecting my lvm2 and devmapper packages, so I'm looking to
>>either give away, or co-maintain the packages w/ someone. Packaging
>>isn't really that hard; most time sucked up by these packages is dealing
>>w/ weird kernel and arch-specific bugs, and coordinating w/ upstream.
>>Knowing C and kernel code is pretty much a must; I don't forsee myself
>>having time to do such things. I'm still willing to help out w/
>>packaging issues, I simply don't have the time to deal w/ bugs like
>>#237409.
>
> That bug is not a bug in the lvm2 package. The lvm2 package just
> contains the binaries to control the kernel dm stuff. It's a kernel
> bug or oversight for the s390 architecture. Bug should be closed or
> reassigned to kernel-image, I guess.
>
> I don't think that you as maintainer of the lvm2 package which
> contains just the lv* / pv* / etc binaries can be expected to
> fix the bugs in the kernel driver (unless you really want to).
>
> Mike.
> --
> Netu, v qba'g yvxr gur cynvagrkg :)
Most of the bugs that lvm2 sees are one of the following:
- 2.4 kernel bugs
- 2.6 kernel bugs
- bugs in the compiler (gcc snapshots, blech) used to compile the kernel
- bugs in the compiler used to compile lvm2/devmapper
- lack of support for some random feature in 2.6
Of course, I need to go through each and identify which they are, and
which section of code they actually come from (otherwise we play the blame
game, reassigning bugs back and forth). This is time consuming, and I
haven't had time for it lately.
Reply to: