<div dir="ltr">Hi Andrew,<div><br></div><div>Thanks for your e-mail.</div><div>>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.</div><div>I thought that setting the parameter RTEMS_FILESYSTEM_READ_WRITE in the function call below would do the job:</div><div> if (mount_and_make_target_path(devname,<br> "/TFTP/",<br> RTEMS_FILESYSTEM_TYPE_TFTPFS,<br> RTEMS_FILESYSTEM_READ_WRITE,<br> NULL))<br></div><div><br></div><div>I am able to write the file using tftp from my linux system. When I examine the tftp log file then I do not see any attempt from the RTEMS system to request the file to be written so I suspect that it is a certain configuration in EPICS/RTEMS missing?</div><div><br></div><div>>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.</div><div>Our IT guys tried and they said that NFS V2 can not be used on RL8. This surprises me since it is fine on RHEL-8 according to your statement and also:</div><div><a href="https://epics.anl.gov/tech-talk/2022/msg00267.php">https://epics.anl.gov/tech-talk/2022/msg00267.php</a><br></div><div><br></div><div>Best Regards</div><div>Mirek</div><div><br></div><div><br></div><div> </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">śr., 14 lut 2024 o 11:02 Johnson, Andrew N. <<a href="mailto:anj@anl.gov">anj@anl.gov</a>> napisał(a):<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="auto">
Hi Mirek,
<div><br>
</div>
<div>TFTP is normally only used for reading, and it doesn’t surprise me if writing isn’t supported since there is no user <span style="color:rgb(0,0,0)">authentication </span><span style="color:rgb(0,0,0)">involved.</span></div>
<div><span style="color:rgb(0,0,0)"><br>
</span></div>
<div>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.</div>
<div><br>
</div>
<div>V2 will be removed from the upstream <a href="http://kernel.org" target="_blank">kernel.org</a> 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…</div>
<div><br>
</div>
<div>- Andrew</div>
<div>
<div dir="ltr">
<div><br>
</div>
<div>-- </div>
<div>Complicity is easy, Simplexity takes real work</div>
</div>
<div dir="ltr"><br>
<blockquote type="cite">On Feb 14, 2024, at 2:23 PM, Miroslaw Dach <<a href="mailto:miroslaw.dach@gmail.com" target="_blank">miroslaw.dach@gmail.com</a>> wrote:<br>
<br>
</blockquote>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">Hello,
<div><br>
</div>
<div>I have two types of the EPICS and RTEMS 4.10 and RTEMS5 bases systems.</div>
<div>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 </div>
<div>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.</div>
<div><br>
</div>
<div>The tftpfs is set as following:</div>
<div><br>
</div>
<div><b><font face="monospace">EPICS_R7.07/base/modules/libcom/RTEMS/posix/rtems_init.c<br>
</font></b></div>
<div><b><font face="monospace"><br>
</font></b></div>
<div><b><font face="monospace">initialize_remote_filesystem(char **argv, int hasLocalFilesystem){<br>
</font></b></div>
<div><b><font face="monospace">:</font></b></div>
<div><b><font face="monospace"> if (mount_and_make_target_path(devname,<br>
"/TFTP/",<br>
RTEMS_FILESYSTEM_TYPE_TFTPFS,<br>
RTEMS_FILESYSTEM_READ_WRITE,<br>
NULL))<br>
perror("mount_and_make_target_path");<br>
</font></b></div>
<div><b><font face="monospace">:</font></b></div>
<div><b><font face="monospace">}</font></b></div>
<div><br>
</div>
<div>When I try to write a file I get a following error:</div>
<div><font face="monospace"><b>dbl > S0817PVs.txt<br>
st.cmd line 60: Can't open "S0817PVs.txt": I/O error.</b></font><br>
</div>
<div><br>
</div>
<div>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 .</div>
<div><br>
</div>
<div>Does anybody have any advice?</div>
<div><br>
</div>
<div>Best Regards</div>
<div>Mirek</div>
<div><br>
</div>
<div><br>
</div>
</div>
<span>_______________________________________________</span><br>
<span>users mailing list</span><br>
<span><a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a></span><br>
<span><a href="http://lists.rtems.org/mailman/listinfo/users" target="_blank">http://lists.rtems.org/mailman/listinfo/users</a></span></div>
</blockquote>
</div>
</div>
</blockquote></div>