linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "RSR - Piero Dominioni" <pdominioni@rsr.it>
To: "Jean-Denis Boyer" <jdboyer@mediatrix.com>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: R: NFS mount for TQM823L
Date: Thu, 4 Oct 2001 16:58:20 +0200	[thread overview]
Message-ID: <00d201c14ce5$069d5300$7e7e7e7e@server> (raw)
In-Reply-To: F1BED55F35F4D3118C0F00E0295CFF4D414C24@mail.mediatrix.com


> Be sure that the file '/etc/services' in the target includes the following
> entries:
>  sunrpc   111/tcp   portmapper   # RPC 4.0 portmapper TCP
>  sunrpc   111/udp   portmapper   # RPC 4.0 portmapper UDP

> Also, be sure you have the file '/etc/rpc' present in the target.

Dear Jean-Denis,
I must be pretty unlucky or a bit stupid since I couldn't remote-mount
my target filesystem yet!
I followed your instuctions: effectively I had neither the entries shown
above nor rpc file on my target.
Trying to do the best I copied the /etc/rpc file from the host to
the target: the problem is not solved yet.
We cross-compiled 'rpcinfo' command, but running it on the target
we obtain:

rpcinfo: can't contact portmapper: RPC: remote system error - Invalid
argument

While if we remote-execute it with
# rpcinfo -p 126.126.126.107  (our target's IP)
from the host's command line prompt we correctly obtain
program    vers    proto    port
100000        2        tcp        111    portmapper
100000        2        udp       111    portmapper

(Running the rpcinfo command on the host, it shows mountd
and nfsd ports too...)
Once again if we try '# ./mountd' we obtain

Cannot register service: RPC: Unable to send, errno = Invalid argument

At this point I can only make suppositions.
There is very little information about portmapper in all the documentation,
books and HOWTOs I looked in, and I read about a 'RPC server'.
Nevertheless I could find no remainders to it looking around
on my PC Linux Box nor something similar.
Is there a RPC server that I didn't start yet?
I feel not yet desperate, but this fight is exhausting...!
Thank you very much for your help.

Best regards.

Piero Dominioni
R.S.R. srl


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-10-04 14:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-02 14:32 NFS mount for TQM823L Jean-Denis Boyer
2001-10-04 14:58 ` RSR - Piero Dominioni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-09 15:57 Jean-Denis Boyer
2001-10-11 13:15 ` R: " RSR - Piero Dominioni
2001-10-04 16:25 Jean-Denis Boyer
2001-10-08 14:33 ` R: " RSR - Piero Dominioni
2001-09-27 15:03 Jean-Denis Boyer
2001-10-01 11:02 ` R: " RSR - Piero Dominioni
2001-09-27 12:52 Jean-Denis Boyer
2001-09-27 14:42 ` R: " RSR - Piero Dominioni

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='00d201c14ce5$069d5300$7e7e7e7e@server' \
    --to=pdominioni@rsr.it \
    --cc=jdboyer@mediatrix.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 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).