From: "lim.taicom" <lim.taicom@gmail.com>
To: linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>
Cc: linux-arch@vger.kernel.org,
linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: lim_nfs problem
Date: Tue, 21 Aug 2007 11:21:40 +0800 [thread overview]
Message-ID: <200708211121367633321@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 469 bytes --]
hello:
I have some question when I use nfs on my own board.
but there is some error like this:
Root-NFS: Server returned error -13 while mounting /home/lim/Ramdisk
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or 02:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 02:00
But in my nfs server ,i can use mount -t nfs localhost:/home/lim/Ramdisk to everywhere i want
what is problem?
[-- Attachment #2: man_010.gif --]
[-- Type: image/gif, Size: 1998 bytes --]
reply other threads:[~2007-08-21 3:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200708211121367633321@gmail.com \
--to=lim.taicom@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-embedded@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).