All of lore.kernel.org
 help / color / mirror / Atom feed
From: chris@basementcode.com (Christopher Harvey)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Init error NFS booting a Fedora 13 file system
Date: Mon, 16 May 2011 14:26:37 -0500	[thread overview]
Message-ID: <c612c4d4201652f45ead46977a099592@basementcode.com> (raw)
In-Reply-To: <BANLkTinGLZj-DEjb2aq_d6r-FA1nd9pPNQ@mail.gmail.com>

 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.

      reply	other threads:[~2011-05-16 19:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-13 16:06 Init error NFS booting a Fedora 13 file system Erlon Cruz
2011-05-13 17:20 ` chris at basementcode.com
2011-05-13 17:45   ` Erlon Cruz
2011-05-13 17:58     ` Erlon Cruz
2011-05-13 19:14       ` Christopher Harvey
2011-05-16 19:18         ` Erlon Cruz
2011-05-16 19:26           ` Christopher Harvey [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c612c4d4201652f45ead46977a099592@basementcode.com \
    --to=chris@basementcode.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.