Re: [gentoo-user] genkernel assistance building initramfs

[Michael Scherer]

So you solved it.
It would be nice then to adorn your subject lines with a [solved] tag,
to avoid further getting mails with comments that are obsolete.

michael

-- 
Michael Scherer
Univ.klinik f. Psychiatrie
email: michael.scherer@×××××××××××××.at
phone: [phone]

----- Original Message ----- 
From: "Dale" <rdalek1967@×××××.com>
To: <gentoo-user@l.g.o>
Sent: Tuesday, 24 April, 2012 01:43
Subject: Re: [gentoo-user] genkernel assistance building initramfs


> Michael Scherer wrote:
>> On Mon, 23 Apr 2012 18:01:09 -0500
>> Dale <rdalek1967@×××××.com> wrote:
>>
>>> Michael Scherer wrote:
>>>> On Mon, 23 Apr 2012 13:26:57 -0500
>>>> Dale <rdalek1967@×××××.com> wrote:
>>>>
>>>>> Michael Mol wrote:
>>>>>> So, my habit is to have /usr sit on top of LVM on top of mdraid. I
>>>>>> really don't want to get into the business of manually managing my
>>>>>> own initramfs, and udev >= 181 will eventually hit stable. I want
>>>>>> my systems ready before that.
>>>>>>
>>>>>> Now, having looked at the pertinent documentation, it looks like
>>>>>> the command I need to run is:
>>>>>>
>>>>>> genkernel --lvm --mdadm --disklabel initramfs
>>>>>>
>>>>>> and then add the initramfs to my grub setup.
>>>>>>
>>>>>> The trouble is, genkernel dies on me. I tried for some feedback in
>>>>>> #gentoo-chat, and DrEeevil gave me two clues:
>>>>>>
>>>>>> 13:34 <+DrEeevil> that shouldn't even be possible
>>>>>> 13:36 <+DrEeevil> mikemol: looks like static linking didn't on
>>>>>> your system
>>>>>>
>>>>>> I don't know where to take things from here. I'm hesitant to file
>>>>>> a bug on b.g.o, because the tail end of genkernel.log specifically
>>>>>> says not to file build errors as bug reports.
>>>>>>
>>>>>> So...any ideas? This is an amd64 mostly-stable system, and dracut
>>>>>> is still masked on amd64, which is why I'm trying to get genkernel
>>>>>> working.
>>>>>>
>>>>>> I've attached genkernel.log
>>>>>>
>>>>>
>>>>>
>>>>> If I read the -dev mailing list correctly, they plan to still
>>>>> support /usr without a init thingy.  After all the mess I went
>>>>> through, we may not need the init thingy after all.
>>>>>
>>>>> Go figure.
>>>>>
>>>>> Dale
>>>>>
>>>>> :-)  :-)
>>>>>
>>>>
>>>> I wouldn't bet on that.
>>>>
>>>> But there is a detailed gentoo howto to create an iniramfs
>>>> that does just that: load /usr.
>>>> http://wiki.gentoo.org/wiki/Early_Userspace_Mounting
>>>> It works. You only need tell your bootloader that now you
>>>> have an initramfs.
>>>> There's also a more general introduction
>>>> http://en.gentoo-wiki.com/wiki/Initramfs
>>>> for a lot of other options
>>>>
>>>> michael
>>>>
>>>>
>>>
>>>
>>> I'm not betting on it but that is what the Gentoo council voted on and
>>> it said that /usr on a separate partition was going to be supported.
>>>
>>> You must have missed the HUGE thread where I was trying to get a init
>>> thingy to work huh?
>>>
>>> Dale
>>>
>>> :-)  :-)
>>>
>>
>> Indeed, I missed all but one email, but there was no hint
>> at all that anything had been said before I came in.
>> Sorry for my unsolicited comments, and I hope you have
>> solved that problem in one or another way.
>>
>> michael
>>
>>
>>
>
>
> I meant to put a "LOL" after the comment about the huge thread.  I'm not
> sure how I missed that.  :/   I did get it to work finally.  It took
> several peoples help and a hammer on my part.  ;-)
>
> I'm just curious as to how they are going to support this in the future.
> I have read where some say it can be done but others say it can't, or
> not easily.  Old saying, this is where the rubber meets the road.  ^_^
>
>
> To the OP.  I would use dracut.  I ran into trouble but I found out
> later that a earlier attempt at a init thingy was causing the dracut
> init thingy to mess up.  I strongly suspect that if I had known to get
> rid of the previous attempt, it would have worked the first time.  My
> previous attempt was the one that was built into the kernel itself.
> Lets just say there was a huge fight and I missed it.  Grub was telling
> one thing to load and the kernel was trying to load something else.  I'm
> sure it was a nice fight.
>
> Dale
>
> :-)  :-)
>
> --
> I am only responsible for what I said ... Not for what you understood or
> how you interpreted my words!
>
> Miss the compile output?  Hint:
> EMERGE_DEFAULT_OPTS="--quiet-build=n"
>
>