Re: system gets stuck in a lock during boot

["Justin P. Mattock" <justinmattock@gmail.com>]

Steven Rostedt wrote:
> On Wed, 2009-10-07 at 07:53 -0700, Justin P. Mattock wrote:
>    
>> Steven Rostedt wrote:
>>      
>>> On Tue, 2009-10-06 at 19:42 -0700, Justin P. Mattock wrote:
>>>
>>>
>>>        
>>>>>
>>>>>            
>>>> o.k. applied your patch, but unfortunantly
>>>> I still am hitting this kernel panic.
>>>>
>>>> must admit I have no idea why this is doing this.
>>>> (but am willing to sit through this, because eventually
>>>> sooner or later will hit this if I update gcc).
>>>>
>>>>          
>>> But the panic you showed was that it could not find an init to execute.
>>> Which looks like a setup issue and not a kernel bug.
>>>
>>> -- Steve
>>>
>>>
>>>
>>>
>>>        
>> That's whats getting me, i.g. if I compile
>> sysvinit normally without adding an SELinux patch
>> the system boots, as soon as I compile sysvinit with
>> SELinux support to load the policy, bam... I hit this.
>>
>> I can send a post to SELinux and see what they think,
>> and the go from there.
>>      
>
> Oh! It's an SELinux thing. It probably prevents you from executing
> init ;-)
>
> -- Steve
>
>
>
>    
What I think is happening is while building
sysvinit with the SELinux patch, sysvinit is looking
in /lib for libselinux(but could be wrong) but libselinux is in
/lib64.
(here's my excuse as a newbie:)
  part of a pain when building an x86_64 multilib is building
everything to point to lib64(pure64 with the soft link
lib64 -> lib makes life so much easier).

I'm going to look at that patch and see how it tells
-lselinux -lsepol to find the libs.
(if this is the case then I must admit I am a real
newbie, and apologize for the confusion).

Justin P. Mattock