Hallo Chris, yes it works as described. The header file (librtemsNfs.h) is also there. I must have done something wrong the day before yesterday. Unfortunately I can't reproduce it anymore. Sorry for the "false alarm”.
I no longer use librtemNfs.h when using the libbsd stack. It is no longer necessary there. For mounting I already use “mount_and_marget_target_path(). This call is ok? If I still need it for the legacy stack I can't try it at the moment. I will try it next week. But I guess that I don't need it at all anymore with RTEMS5. It seems to be a RTEMS 4 remnant. Viele Grüße Heinz > On 25. Aug 2020, at 04:07, Chris Johns <chr...@rtems.org> wrote: > >> >> After that I tried to build EPICS and ran into the error of a missing header >> file. >> “librtemsNFS.h could not be found” >> This header file is in rtems-libbsd which I then had to reinstall and build >> for the target. > > I could not find `librtemsNFS.h` but I found `librtemsNfs.h`? ... > > $ find . -name librtems\*.h > ./cpukit/libnetworking/librtemsNfs.h > >> >> Then I thought about whether a recipe could/should consider this dependency. >> > > The header should be there. I am more concerned about the contents of the that > header ... hmm. > > What calls does EPICS use from this file? I suggest it gets reviewed. The > problem RTEMS has long term with the interface in `librtemsNfs.h` is it being > bespoke to the NFS implementation and we may not be able to maintain it in the > future, for example upgrading NFS to NFSv4. > > In systems I work on for clients I encourage scripting of some form be used. > Commands hide the implementation details and this lets us (RTEMS) better > maintain compatibility. The scripting can be plain text files or `joel` > scripts > or command sequences in another configuration format, for example YAML. You > can > directly call shell commands. > > To mount a remote disk use: > > mkdir /foobar > mount -t nfs foo:/bar /foobar > > Chris
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel