Summary: | LILO doesn't know about device-mapper (with patch!) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | toon <toon> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | max, wschlich |
Priority: | Normal | ||
Version: | 1.4 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
This is the modified ebuild script by Christophe Saout <christophe@saout.de>
This is the digest file that goes with the modified ebuild script. This is the patch to LILO |
Description
toon
2003-11-19 15:28:19 UTC
Created attachment 20961 [details] This is the modified ebuild script by Christophe Saout <christophe@saout.de> Two more attachments coming up. Regards, Toon. Created attachment 20962 [details]
This is the digest file that goes with the modified ebuild script.
One more attachment coming up.
Created attachment 20963 [details, diff] This is the patch to LILO That's it! All credits go to Christophe Saout <christophe@saout.de> Regards, Toon. On more thing, you can find my original detailed bug report at: http://lists.sistina.com/pipermail/dm-devel/2003-November/000317.html Just guessing on the maintainer. Christophe Saout made this remark when he sent me the patch: "I'm sure someone can come up with an ebuild file that sets the define depending on the availability of libdevmapper or something." So this is probably something extra that has to be done. max, you handle lvm2 it looks like -- is lvm2 exclusively a 2.6 thing? in other words can we just do the switch on kernel version 2.6 to apply this patch? actually, on warpzero's suggestion, I'll use a local USE flag called devmapr to enable this patch I use device-mapper/lvm2 on custom 2.4 with the dm patch (and some other stuff). Enabling this via a use flag is probably the best approach, though I am not entirely comfortable with a use flag named 'devmapr'. How about lvm2 or dm? But in any case, that is for the maintainer of lilo to decide. I think this bug can be closed. I agree, this can be closed. Device mapper functionality has been in the lilo ebuild for two release cycles now. |