On 10/31/2016 10:26 AM, Michael Davidsaver wrote:
> Unless you are prepared to do, or sponsor, some work the only realistic
> option for RTEMS is NFSv3.
I should clarify. The RTEMS NFS client speaks only version 2 over UDP,
while the Linux NFS server (which I've always used) speaks both v2, v3,
and now v4 over both UDP and TCP transports. To check which versions an
NFS server supports run:
> $ /usr/sbin/rpcinfo -p localhost|grep nfs
> 100003 2 tcp 2049 nfs
> 100003 3 tcp 2049 nfs
> 100003 4 tcp 2049 nfs
> 100003 2 udp 2049 nfs
> 100003 3 udp 2049 nfs
> 100003 4 udp 2049 nfs
The important line for RTEMS being
> 100003 2 udp 2049 nfs
Of course individual mounts must still be exported in a way (host ACL)
which allows a v2/3 client to mount them.
- References:
- Re: Error with RTEMS on MVME5500 "भावना नितिन मेढ़"
- Re: Error with RTEMS on MVME5500 Michael Davidsaver
- Navigate by Date:
- Prev:
quadEM R7-0 now available Mark Rivers
- Next:
EPICS Base Release-Candidate Double Feature! Andrew Johnson
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Error with RTEMS on MVME5500 Michael Davidsaver
- Next:
areaDetector and ADCore R2-5 released Mark Rivers
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
2024
|