On Tue, Apr 24, 2012 at 11:35 AM, Dale <rdalek1...@gmail.com> wrote: > Michael Mol wrote: >> On Tue, Apr 24, 2012 at 11:06 AM, Dale <rdalek1...@gmail.com> wrote: >> >> [snip] >> >>> I might also add, genkernel is stable and has been for ages. It's been >>> a while since I tried it but the last time I did, it failed miserably. >>> It 'claimed' everything worked fine but when I booted, it failed. I got >>> the old blinky keyboard lights treatment. :/ >>> >>> Just because something isn't marked stable doesn't mean it doesn't work. >>> I would guess that half the stuff on my system as I type, is not >>> stable. That would include all of KDE, portage and related tools plus >>> no telling how many other deps that got pulled in. >> >> Oh, certainly. Sometimes, I have to unmask packages (or versions >> thereof) because I know of upstream fixes I want or need. >> >> As a general rule, though, I avoid doing it unless I have specific, >> strong and compelling need. >> > > This could be one of those times. The trouble I ran into became clear > later on. I had tried to build a init thingy that was built into the > kernel. It didn't work right so I left it behind. Thing is, I forgot > to disable that in the kernel config. So, I was building a kernel with > a broken init thingy and telling grub to use the init thingy built by > dracut. Can you imagine the fist fight that was being had?
I followed the thread; there's very little on this list I don't read, or at least skim. :) > > I type all that to say this, unmask dracut, run dracut, add the init > thingy to your grub line. I'm more sure that it will work than I am of > genkernel. I'm pretty stubborn, and I tend to follow a depth-first search algorithm while debugging, backtracking only when I hit a dead end. It can take me longer than, say, a distro-hopper, but I like that I come out with a better understanding of whatever it is I've been banging my head on. The genkernel docs say that if static versions of the requisite packages don't exist, it will build them. If adding the 'static' USE flags under /etc/portage/package.use fixes this use case of genkernel, then I've got a valid bug to report, and the thing can get fixed. -- :wq