From mboxrd@z Thu Jan  1 00:00:00 1970
From: chris@basementcode.com (Christopher Harvey)
Date: Mon, 16 May 2011 14:26:37 -0500
Subject: Init error NFS booting a Fedora 13 file system
In-Reply-To: <BANLkTinGLZj-DEjb2aq_d6r-FA1nd9pPNQ@mail.gmail.com>
References: <BANLkTi=7mbgsR02ajbrbywHeg2XJNXsLMQ@mail.gmail.com>
	<b80e1179ca4376c38b4ef75ebabe3439@basementcode.com>
	<BANLkTimixqJQAMtpXzRX2O+C2LRo7ai_CQ@mail.gmail.com>
	<BANLkTikPzDOw7-cx3pX+oB-6O6zbk_XfYA@mail.gmail.com>
	<80f3ac52e5308fc7e9a85aead7f08c07@basementcode.com>
	<BANLkTinGLZj-DEjb2aq_d6r-FA1nd9pPNQ@mail.gmail.com>
Message-ID: <c612c4d4201652f45ead46977a099592@basementcode.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

 On Mon, 16 May 2011 16:18:23 -0300, Erlon Cruz <sombrafam@gmail.com> 
 wrote:
>> you mean the LD_LIBRARY_PATH?
>
> Yes, I thing that what might  be happening is that when the system is
> in initramfs, LD_LIBRARY_PATH is not set so the system cant execute
> the dynamically linked init. I this config you said you did do you 
> had
> to set any configuration (so set something) after or before 
> chrooting?
>
 If you have a properly setup file system (eg, libraries in /usr/lib and 
 /lib) then you shouldn't need to set and LD_LIBRARY_PATHS during boot or 
 after a chroot. If the chroot gives you errors with regards to 
 libraries, then you've found your problem, otherwise the problem is 
 elsewhere (and the error messages given from trying to run init from a 
 chrooted environment will probably help you).

 I hope that was the original question, you erased the text form the 
 beginning of the email.