EPICS and tftp file system

[Johnson, Andrew N.]

Hi Mirek,

TFTP is normally only used for reading, and it doesn’t surprise me if writing isn’t supported since there is no user authentication involved.

It should be possible to enable NFSv2 in Rocky Linux 8, it still works on RHEL-8 but you do have to change one or two files in the server’s /etc area to do that. Red Hat don’t actually offer support for v2 any more, but they haven’t actively removed the code for it, just disabled it by default.

V2 will be removed from the upstream kernel.org Linux kernel at some point soon and then it will be much harder to continue using, but I don’t think that has happened just yet. Plan for that eventuality…

- Andrew

--
Complicity is easy, Simplexity takes real work

On Feb 14, 2024, at 2:23 PM, Miroslaw Dach <miroslaw.dach at gmail.com> wrote:


Hello,

I have two types of the EPICS and RTEMS 4.10 and RTEMS5 bases systems.
They all use the nfs v2 mount points on the Linus remote host. We current mirage in our lab to the newer version of the LINUX os (Rocky Linux 8) which seems to not support NFS V2. Since I can not migrate to the RTEMS6 and EPICS 7 with some legacy systems due to the drivers incompatibilities
I explored the TFTPFS instead of the NFSFS. All works fine when reading files through tftp. I can't however write files using the tftp.

The tftpfs is set as following:

EPICS_R7.07/base/modules/libcom/RTEMS/posix/rtems_init.c

initialize_remote_filesystem(char **argv, int hasLocalFilesystem){
:
  if (mount_and_make_target_path(devname,
                               "/TFTP/",
                               RTEMS_FILESYSTEM_TYPE_TFTPFS,
                               RTEMS_FILESYSTEM_READ_WRITE,
                               NULL))
       perror("mount_and_make_target_path");
:
}

When I try to write a file I get a following error:
dbl > S0817PVs.txt
st.cmd line 60: Can't open "S0817PVs.txt": I/O error.

I do not see anything in the tftp log file that the EPICS iocs server even tries to send a request to save a file. It looks like it is something internal in EPICS/RTEMS .

Does anybody have any advice?

Best Regards
Mirek


_______________________________________________
users mailing list
users at rtems.org
http://lists.rtems.org/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20240214/aae119e1/attachment.htm>