R: NFS mount for TQM823L

R: NFS mount for TQM823L

[RSR - Piero Dominioni]

< The portmapper (portmap) and the lock daemon (rpc.lockd) are not running
on
< your target.
< Either you start them, or just add option "-o nolock" when calling mount.
<  # mount -o nolock -t nfs 126.126.126.106:/home /tmp

Thank you, Jean-Denis,
but your hint is correct only in one direction:
giving your command

  # mount -o nolock -t nfs 126.126.126.106:/home /tmp

from the target's command line prompt to mount the remote host's
"/home" directory under the local filesystem the error messages
don't appear anymore.
But it seems not to be enough in the opposite direction:
the command

  # mount -o nolock -t nfs 126.126.126.107:/  /tmp

given from host's command line prompt to mount the remote
target's "/" directory (that is the whole filesystem) under the local
filesystem obtains the same error message I got without the
"nolock" option.
[Note: 126.126.126.107 is the target's IP address,
while 126.126.126.106 is host's one!]
What else is wrong or still missing now?
However thank you for your help.

Best regards

Piero Dominioni
R.S.R.srl


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

R: NFS mount for TQM823L

[RSR - Piero Dominioni]

I need your help anymore:

< You need the portmapper (portmap), NFS daemon (rpc.nfsd), NFS mount daemon
< (rpc.mountd).
< All this comes from the standard NFS control script.
< Refers to the nfs-utils package (http://sourceforge.net/projects/nfs/)
< in the script file 'etc/nodist/nfs-server'.

I downloaded the nfs-utils-0.3.3.tar.gz, compiled for pc and used the
portmap daemon obtained this way on my Slackware 7.2 Linux box
(The executable file is quite double in dimensions respect the one
installed and temporarily substituted on my Linux box).
Everything works fine.

Then I cross-compiled it and, since I didn't well understand what to do
with the nfs-server script, I used nfsd and mountd found under
nfs-utils-0.3.3/utils/nfsd/  (.../utils/mountd/).
I transferred these three files on my target (TQM823L) via ftp, then:
# chmod 755 portmap     // the same for nfsd and mountd
# ./portmap
# ps aux
I can see that portmap is suspended: I guess it is correctly waiting for
RPC calls and for other daemons (such as mountd and nfsd) to register.

But if I try to run mountd or nfsd (# ./mountd,  for example) I get the same
errors as portmap wouldn't be running at all.
Why? What should I do anymore?

< I'm not sure, but you may also need the remote quota server (rpc.rquotad).
< Of course, you should have a valid /etc/exports file.

I didn't try quotad: if mountd and nfsd don't run maybe it wouldn't too...

< You can even use it directly to start the NFS server.

Can you explain me how?
Should I cross-compile it for my PowerPC platform, load it on the targe
and then run it?

Thank you very much for your patience.

Best regards

Piero Dominioni
R.S.R. srl


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

R: NFS mount for TQM823L

[RSR - Piero Dominioni]

> 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/

RE: NFS mount for TQM823L

[Jean-Denis Boyer]

> Try:
>   ipconfig lo 127.0.0.1

Well, of course, I meant 'ifconfig', not 'ipconfig'.
I can't remember where this mistake comes from... ;-)

--------------------------------------------
 Jean-Denis Boyer, B.Eng., Technical Leader
 Mediatrix Telecom Inc.
 4229 Garlock Street
 Sherbrooke (Québec)
 J1L 2C8  CANADA
 (819)829-8749 x241
--------------------------------------------

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

R: NFS mount for TQM823L

[RSR - Piero Dominioni]

[-- Attachment #1: Type: text/plain, Size: 2929 bytes --]

> > Try:
> >   ipconfig lo 127.0.0.1

> Well, of course, I meant 'ifconfig', not 'ipconfig'.
> I can't remember where this mistake comes from... ;-)

Dear Jean-Denis,
I think we're very close to the end, but not there yet!
I send you in attach the 'rpc' and 'services' files I loaded
on the target (I hand-wrote them first, unsuccessfully:
I copied then these ones from the host).
Here is what I type and obtain now.

/ # ifconfig lo 127.0.0.1
/ # /sbin/portmap
/ # rpcinfo -p
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
/ # /sbin/mountd
/ # /sbin/nfsd
/ # ps aux
  PID  Uid      Gid State Command
    1 root     root     S init
    2 root     root     S [keventd]
    3 root     root     S [kswapd]
    4 root     root     S [kreclaimd]
    5 root     root     S [bdflush]
    6 root     root     S [kupdated]
    9 root     root     R -sh
   12 root     root     S /sbin/inetd -i
   75 root     root     S /bin/sh /bin/application
   77 root     root     S sleep 500
   80 bin      root     S /sbin/portmap
   84 root     root     S [nfsd]
   85 root     root     S [lockd]
   86 root     root     S [rpciod]
   87 root     root     R ps aux
/ # rpcinfo -p
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100005    1   udp   2048  mountd
    100005    1   tcp   2048  mountd
    100005    2   udp   2048  mountd
    100005    2   tcp   2048  mountd
    100005    3   udp   2048  mountd
    100005    3   tcp   2048  mountd
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100021    1   udp   2048  nlockmgr
    100021    3   udp   2048  nlockmgr
    100021    4   udp   2048  nlockmgr

(Note that I type the 'mountd' command, but it doesn't
appear in the ps -aux output list!)
While if I type the same command for the host the
mountd uses a different port number...

/ # rpcinfo -p 126.126.126.106
   program vers proto   port
    100000    2   tcp    111  portmapper
    100000    2   udp    111  portmapper
    100005    1   udp    672  mountd
    100005    2   udp    672  mountd
    100005    1   tcp    675  mountd
    100005    2   tcp    675  mountd
    100003    2   udp   2049  nfs
    100003    2   tcp   2049  nfs
/ #

Your indications were once more correct: after to have
added the 'ifconfig' command to the target's busybox
(ver. 0.51) and to run it as you told me, 'rpcinfo -p' works fine.
But if I try to mount the target's filesystem from the host, with
/ # mount -t nfs 126.126.126.107:/  /mydir
on the host's console I get

mount: RPC: Program unavailable

while, exactly meantime, the following message appears
on the target's console:

svc: unknown program 100005 (me 100021)

I trust that your experience lets you understand
these messages better than me!
Waiting for your punctual answer...
Thank you.

Best regards.

Piero Dominioni
R.S.R. srl



[-- Attachment #2: services --]
[-- Type: application/octet-stream, Size: 6111 bytes --]

#
# Network services, Internet style
#
# Note that it is presently the policy of IANA to assign a single well-known
# port number for both TCP and UDP; hence, most entries here have two entries
# even if the protocol doesn't support UDP operations.
# Updated from RFC 1340, ``Assigned Numbers'' (July 1992).  Not all ports
# are included, only the more common ones.
#
#	from: @(#)services	5.8 (Berkeley) 5/9/91
#	$Id: services,v 1.9 1993/11/08 19:49:15 cgd Exp $
#
tcpmux		1/tcp		# TCP port service multiplexer
echo		7/tcp
echo		7/udp
discard		9/tcp		sink null
discard		9/udp		sink null
systat		11/tcp		users
daytime		13/tcp
daytime		13/udp
netstat		15/tcp
qotd		17/tcp		quote
msp		18/tcp		# message send protocol
msp		18/udp		# message send protocol
chargen		19/tcp		ttytst source
chargen		19/udp		ttytst source
ftp-data        20/tcp          # File Transfer [Default Data]
ftp-data        20/udp          # File Transfer [Default Data]
ftp             21/tcp          # File Transfer [Control]
ftp             21/udp          # File Transfer [Control]
ssh             22/tcp          # Secure Shell Login
ssh             22/udp          # Secure Shell Login
telnet          23/tcp
telnet          23/udp
# 24 - private
smtp		25/tcp		mail
# 26 - unassigned
time		37/tcp		timserver
time		37/udp		timserver
rlp		39/udp		resource	# resource location
nameserver	42/tcp		name		# IEN 116
whois		43/tcp		nicname
domain		53/tcp		nameserver	# name-domain server
domain		53/udp		nameserver
mtp		57/tcp				# deprecated
bootps		67/tcp		# BOOTP server
bootps		67/udp
bootpc		68/tcp		# BOOTP client
bootpc		68/udp
tftp		69/udp
gopher		70/tcp		# Internet Gopher
gopher		70/udp
rje		77/tcp		netrjs
finger		79/tcp
www		80/tcp		http	# WorldWideWeb HTTP
www		80/udp			# HyperText Transfer Protocol
link		87/tcp		ttylink
kerberos	88/tcp		krb5	# Kerberos v5
kerberos	88/udp
supdup		95/tcp
# 100 - reserved
hostnames	101/tcp		hostname	# usually from sri-nic
iso-tsap	102/tcp		tsap		# part of ISODE.
csnet-ns	105/tcp		cso-ns	# also used by CSO name server
csnet-ns	105/udp		cso-ns
rtelnet		107/tcp		# Remote Telnet
rtelnet		107/udp
pop2		109/tcp		postoffice	# POP version 2
pop2		109/udp
pop3		110/tcp		# POP version 3
pop3		110/udp
sunrpc		111/tcp
sunrpc		111/udp
auth		113/tcp		tap ident authentication
sftp		115/tcp
uucp-path	117/tcp
nntp		119/tcp		readnews untp	# USENET News Transfer Protocol
ntp		123/tcp
ntp		123/udp				# Network Time Protocol
netbios-ns	137/tcp				# NETBIOS Name Service
netbios-ns	137/udp
netbios-dgm	138/tcp				# NETBIOS Datagram Service
netbios-dgm	138/udp
netbios-ssn	139/tcp				# NETBIOS session service
netbios-ssn	139/udp
imap2		143/tcp				# Interim Mail Access Proto v2
imap2		143/udp
snmp		161/udp				# Simple Net Mgmt Proto
snmp-trap	162/udp		snmptrap	# Traps for SNMP
cmip-man	163/tcp				# ISO mgmt over IP (CMOT)
cmip-man	163/udp
cmip-agent	164/tcp
cmip-agent	164/udp
xdmcp		177/tcp				# X Display Mgr. Control Proto
xdmcp		177/udp
nextstep	178/tcp		NeXTStep NextStep	# NeXTStep window
nextstep	178/udp		NeXTStep NextStep	# server
bgp		179/tcp				# Border Gateway Proto.
bgp		179/udp
prospero	191/tcp				# Cliff Neuman's Prospero
prospero	191/udp
irc		194/tcp				# Internet Relay Chat
irc		194/udp
smux		199/tcp				# SNMP Unix Multiplexer
smux		199/udp
at-rtmp		201/tcp				# AppleTalk routing
at-rtmp		201/udp
at-nbp		202/tcp				# AppleTalk name binding
at-nbp		202/udp
at-echo		204/tcp				# AppleTalk echo
at-echo		204/udp
at-zis		206/tcp				# AppleTalk zone information
at-zis		206/udp
z3950		210/tcp		wais		# NISO Z39.50 database
z3950		210/udp		wais
ipx		213/tcp				# IPX
ipx		213/udp
imap3		220/tcp				# Interactive Mail Access
imap3		220/udp				# Protocol v3
ulistserv	372/tcp				# UNIX Listserv
ulistserv	372/udp
#
# UNIX specific services
#
exec		512/tcp
biff		512/udp		comsat
login		513/tcp
who		513/udp		whod
shell		514/tcp		cmd		# no passwords used
syslog		514/udp
printer		515/tcp		spooler		# line printer spooler
talk		517/udp
ntalk		518/udp
route		520/udp		router routed	# RIP
timed		525/udp		timeserver
tempo		526/tcp		newdate
courier		530/tcp		rpc
conference	531/tcp		chat
netnews		532/tcp		readnews
netwall		533/udp				# -for emergency broadcasts
uucp		540/tcp		uucpd		# uucp daemon
remotefs	556/tcp		rfs_server rfs	# Brunhoff remote filesystem
klogin		543/tcp				# Kerberized `rlogin' (v5)
kshell		544/tcp				# Kerberized `rsh' (v5)
kerberos-adm	749/tcp				# Kerberos `kadmin' (v5)
#
webster		765/tcp				# Network dictionary
webster		765/udp
#
# From ``Assigned Numbers'':
#
#> The Registered Ports are not controlled by the IANA and on most systems
#> can be used by ordinary user processes or programs executed by ordinary
#> users.
#
#> Ports are used in the TCP [45,106] to name the ends of logical
#> connections which carry long term conversations.  For the purpose of
#> providing services to unknown callers, a service contact port is
#> defined.  This list specifies the port used by the server process as its
#> contact port.  While the IANA can not control uses of these ports it
#> does register or list uses of these ports as a convienence to the
#> community.
#
ingreslock	1524/tcp
ingreslock	1524/udp
prospero-np	1525/tcp		# Prospero non-privileged
prospero-np	1525/udp
rfe		5002/tcp		# Radio Free Ethernet
rfe		5002/udp		# Actually uses UDP only
#
#
# Kerberos (Project Athena/MIT) services
# Note that these are for Kerberos v4, and are unofficial.  Sites running
# v4 should uncomment these and comment out the v5 entries above.
#
#kerberos	750/udp		kdc	# Kerberos (server) udp
#kerberos	750/tcp		kdc	# Kerberos (server) tcp
krbupdate	760/tcp		kreg	# Kerberos registration
kpasswd		761/tcp		kpwd	# Kerberos "passwd"
#klogin		543/tcp			# Kerberos rlogin
eklogin		2105/tcp		# Kerberos encrypted rlogin
#kshell		544/tcp		krcmd	# Kerberos remote shell
#
# Unofficial but necessary (for NetBSD) services
#
supfilesrv	871/tcp			# SUP server
supfiledbg	1127/tcp		# SUP debugging

[-- Attachment #3: rpc --]
[-- Type: application/octet-stream, Size: 1663 bytes --]

#ident	"@(#)rpc	1.11	95/07/14 SMI"	/* SVr4.0 1.2	*/
#
#	rpc
#
portmapper	100000	portmap sunrpc rpcbind
rstatd		100001	rstat rup perfmeter rstat_svc
rusersd		100002	rusers
nfs		100003	nfsprog
ypserv		100004	ypprog
mountd		100005	mount showmount
ypbind		100007
walld		100008	rwall shutdown
yppasswdd	100009	yppasswd
etherstatd	100010	etherstat
rquotad		100011	rquotaprog quota rquota
sprayd		100012	spray
3270_mapper	100013
rje_mapper	100014
selection_svc	100015	selnsvc
database_svc	100016
rexd		100017	rex
alis		100018
sched		100019
llockmgr	100020
nlockmgr	100021
x25.inr		100022
statmon		100023
status		100024
bootparam	100026
ypupdated	100028	ypupdate
keyserv		100029	keyserver
sunlink_mapper	100033
tfsd		100037
nsed		100038
nsemntd		100039
showfhd		100043	showfh
ioadmd		100055	rpc.ioadmd
NETlicense	100062
sunisamd	100065
debug_svc 	100066  dbsrv
ypxfrd		100069  rpc.ypxfrd
bugtraqd	100071
kerbd		100078
event		100101	na.event	# SunNet Manager
logger		100102	na.logger	# SunNet Manager
sync		100104	na.sync
hostperf	100107	na.hostperf
activity	100109	na.activity	# SunNet Manager
hostmem		100112	na.hostmem
sample		100113	na.sample
x25		100114	na.x25
ping		100115	na.ping
rpcnfs		100116	na.rpcnfs
hostif		100117	na.hostif
etherif		100118	na.etherif
iproutes	100120	na.iproutes
layers		100121	na.layers
snmp		100122	na.snmp snmp-cmc snmp-synoptics snmp-unisys snmp-utk
traffic		100123	na.traffic
nfs_acl		100227
sadmind		100232
nisd		100300	rpc.nisd
nispasswd	100303	rpc.nispasswdd
ufsd		100233	ufsd
pcnfsd		150001	pcnfs
amd		300019  amq
bwnfsd		545580417
fypxfrd		600100069 freebsd-ypxfrd

R: NFS mount for TQM823L

[RSR - Piero Dominioni]

> 3) You may also start the syslog daemon, to be sure you don't miss
important
> information.

Dear Jean-Denis,
this above has been the key suggestion that lead me to success!!!
Finally we could remote-mount our target's file system
under whatever host (not every one, really) in our local network!
Without the syslogd daemon I couldn't have been able to
discover that the 'etab' file was missing in /var/lib/nfs target's
directory.
I don't know the rule or the meaning of all the lines and keywords
that are in this file: I would like to know ,  in addition to the
capability to make them run...
Who does create this file, on the hosts for example?
 Which command or daemon?
I add here another pair of question, that would complete the
scene.

> 1) Does it produce a core file?
What do you mean with 'core file'?

> 2) You may start mountd with the following options:
>    mountd --debug all --foreground
>   This will start mountd in foregroud, turning on debugging information.
>    I hope it will help...
How should I have debugged then? (I couldn't do it)
I have seen nothing: should any message have appeared?

At last I want to thank you very much for your precious help, and
I hope that our correspondence could help somebody else.

Best regards

Piero Dominioni
R.S.R. srl


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