Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot root fs over NFS bug
Date: Wed, 29 Jun 2011 16:57:45 +0200	[thread overview]
Message-ID: <20110629165745.01b2aff4@skate> (raw)
In-Reply-To: <4E0B2562.9090208@labri.fr>

Hello,

Please don't reply to me directly, but to the Buildroot list instead.

Le Wed, 29 Jun 2011 15:15:14 +0200,
Jigar SOLANKI <jigar.solanki@labri.fr> a ?crit :

> Thanks a lot for the reply.
> You were absolutely right, my bad, I wasnt mounting my root filesystem
> over NFS, it was just an initramfs.
> 
> I deactivated the initramfs support in the kernel config and it mounts
> just fine.
> 
> My question, just to be sure, is : why the kernel wasnt  mounting it
> before, even if it had everything in his command line (and even if the
> initramfs support was activated ?) It should have mounted it, right ?

If you have an initramfs, then the kernel uncompresses it at boot time,
and executes the /init script/application in this initramfs. And that's
all the kernel does when an initramfs is present: it's the job of the
initramfs initialization procedure to mount the real root filesystem
and switch to it.

So if you have an initramfs, it's normal not to see the typical:

  VFS: Mounted root (nfs filesystem) on device 0:14.

message in your boot log.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      parent reply	other threads:[~2011-06-29 14:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-28 12:27 [Buildroot] Buildroot root fs over NFS bug Jigar SOLANKI
2011-06-28 14:33 ` Thomas Petazzoni
     [not found]   ` <4E0B2562.9090208@labri.fr>
2011-06-29 14:57     ` Thomas Petazzoni [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=20110629165745.01b2aff4@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox