From: Jim Potter <jrp@wvi•com>
To: Paul White <pwhite@bivio•net>
Cc: linuxppc-embedded@lists•linuxppc.org
Subject: Re: NFS client-side components question
Date: Wed, 30 Oct 2002 11:58:09 -0800 [thread overview]
Message-ID: <3DC039D1.370D6B02@wvi.com> (raw)
In-Reply-To: Pine.LNX.4.21.0210281936170.26340-100000@stimpy.bivio.net
Thanks -- that did it for me!
> Jim,
>
> It sounds like its trying to use portmap for locking purposes. Try
> using a -o nolock argument to your mount call, as it sounds like you
> don't have the port mapper installed or running on your ram disk.
> This is what we had to do with ours, and it works great.
>
> Here's what we do:
>
> mount -t nfs -o nolock $SERVER:/home/log /log
>
> Hope this helps..
>
> Paul
>
>
> >
> > 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/
prev parent reply other threads:[~2002-10-30 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-29 0:30 NFS client-side components question Jim Potter
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 [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=3DC039D1.370D6B02@wvi.com \
--to=jrp@wvi$(echo .)com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
--cc=pwhite@bivio$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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