From: Jim Potter <jrp@wvi.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: NFS client-side components question
Date: Mon, 28 Oct 2002 16:30:04 -0800 [thread overview]
Message-ID: <3DBDD68C.CD41E51D@wvi.com> (raw)
I'm developing a moderate sized ramdisk image to be used on an embedded
project, and I'm having trouble getting all of the NFS client-side file
dependencies sorted out on the ramdisk. I'm using YDL installed on
powermacs for my hosts & servers (not cross-hosted from x86 boxes). The
NFS mounts work fine when mounted from another powermac or when the
embedded system is Root-On-NFS booted (both of which have a full YDL
install).
The problem is that when the embedded system is booted to ramdisk, and
then an NFS mount of the server is attempted; the mount command goes
away, and eventually a "portmap: server localhost not responding, timed
out" message pops up. The NFS server box is listed in the /etc/hosts
file.
My ramdisk image has been built by taking various components from a YDL
install; this is so that the target embedded environment (ramdisk) has
compatibility with customer's lab machines (typically YDL boxes). It's
my opinion that I have missed something on the client-side when
assembling the ramdisk image. Does anyone know where I can find a
listing of the dependencies within the various NFS client components
(mount, nfs, rpc, libs, etc)? Thanks, everyone.
--
Sincerely,
Jim Potter
45th Parallel Processing
Firefighting: Bustin' ours, Savin' yours.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-10-29 0:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-29 0:30 Jim Potter [this message]
2002-10-29 2:33 ` about the micro monitor source chete
2002-10-29 3:38 ` NFS client-side components question Paul White
2002-10-30 19:58 ` Jim Potter
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=3DBDD68C.CD41E51D@wvi.com \
--to=jrp@wvi.com \
--cc=linuxppc-embedded@lists.linuxppc.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.