linux-kernel - Re: system gets stuck in a lock during boot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 07 Oct 2009 12:06:22 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	"Justin P. Mattock" <justinmattock@...il.com>
Cc:	Jason Baron <jbaron@...hat.com>, Ingo Molnar <mingo@...e.hu>,
	Peter Zijlstra <peterz@...radead.org>,
	Li Zefan <lizf@...fujitsu.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: system gets stuck in a lock during boot

On Wed, 2009-10-07 at 08:52 -0700, Justin P. Mattock wrote:

> >    
> 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,

Just being able to monkey around with the init code on top of SELinux
already qualifies you to be well beyond a newbie ;-)

-- Steve


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/