Summary: | sys-kernel/genkernel-3.4.10.902: can not include /sbin/cryptsetup to initramfs | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | eddy <agmen> |
Component: | [OLD] Core system | Assignee: | Gentoo Genkernel Maintainers <genkernel> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | brent.saner, bugzilla, candrews, chrissicool, gentoo, ikelos, schism, silvio.frischi |
Priority: | High | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
eddy
2008-12-09 00:31:33 UTC
Whoops. Fixed in git. *** Bug 250825 has been marked as a duplicate of this bug. *** (In reply to comment #0) > this patch fix the problem, it makes the nedded dirs and replace the spelling > mistake. > apply it to /usr/share/genkernel/gen_initramfs.sh > > 289,290d288 > < mkdir -p "${TEMP}/initramfs-luks-temp/lib/bin" > < mkdir -p "${TEMP}/initramfs-luks-temp/lib/sbin" Actually we need the directory "${TEMP}/initramfs-luks-temp/sbin" to be created here, since we copy the cryptsetup binary into it a few lines below. Just another typo, I guess. Fixed How about this version is either removed from portage or masked, since it's pretty obviously broken? Nothing wastes my time like booting to a new kernel only to find the initrd was built with a documented-broken tool and can't decrypt the root filesystem. Yes, ~arch should expect problems, but not persistent, documented brokenness. I just wanted to try out Linus' Christmas present - but failed :| It would be very nice if a new/working version of genkernel would be present in portage soon, because I think many people will stumble upon this issue the next days when they have free time to compile a new kernel. btw: Happy holidays and merry grinding! *** Bug 252684 has been marked as a duplicate of this bug. *** *** Bug 253446 has been marked as a duplicate of this bug. *** This version's now gone from the tree. If 3.4.10.903 solves this problem, this bug can probably be closed... 5:) I usually wait until there's an *actual* release version that fixes the issue, but since it was an issue with a pre-release that's fixed in another pre-release, good enough for me... |