From sebastian.huber at embedded-brains.de  Thu Feb  1 06:47:41 2024
From: sebastian.huber at embedded-brains.de (Sebastian Huber)
Date: Thu, 1 Feb 2024 07:47:41 +0100
Subject: =?UTF-8?B?UmU6IOKAnEFXOuKAnSA/?=
In-Reply-To: <89B3B5B1-1546-42A7-B4B8-57A970F818BC@gmail.com>
References: <89B3B5B1-1546-42A7-B4B8-57A970F818BC@gmail.com>
Message-ID: <8820fe4f-a339-45d7-a910-d95e0453e91f@embedded-brains.de>

On 31.01.24 18:20, John Howard wrote:
> Lost in translation.
> 
> Anybody here know what ?AW:? in the Subject means?
> 
> At first, I took it to mean a comical expression of sarcasm because of an accident.
> 
> Ironically, that?s not it.

It is an abbreviation of Antwort (answer) and was probably produced by 
some super smart software from Redmond.

-- 
embedded brains GmbH & Co. KG
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.huber at embedded-brains.de
phone: +49-89-18 94 741 - 16
fax:   +49-89-18 94 741 - 08

Registergericht: Amtsgericht M?nchen
Registernummer: HRB 157899
Vertretungsberechtigte Gesch?ftsf?hrer: Peter Rasmussen, Thomas D?rfler
Unsere Datenschutzerkl?rung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/

From Jan.Sommer at dlr.de  Thu Feb  1 08:51:26 2024
From: Jan.Sommer at dlr.de (Jan.Sommer at dlr.de)
Date: Thu, 1 Feb 2024 08:51:26 +0000
Subject: =?utf-8?B?UkU6IOKAnEFXOuKAnSA/?=
In-Reply-To: <8820fe4f-a339-45d7-a910-d95e0453e91f@embedded-brains.de>
References: <89B3B5B1-1546-42A7-B4B8-57A970F818BC@gmail.com>
 <8820fe4f-a339-45d7-a910-d95e0453e91f@embedded-brains.de>
Message-ID: <646f70ef348743e2aecaade303733429@dlr.de>



> -----Original Message-----
> From: users <users-bounces at rtems.org> On Behalf Of Sebastian Huber
> Sent: Donnerstag, 1. Februar 2024 07:48
> To: John Howard <echosoft.llc at gmail.com>; users at rtems.org
> Subject: Re: ?AW:? ?
> 
> On 31.01.24 18:20, John Howard wrote:
> > Lost in translation.
> >
> > Anybody here know what ?AW:? in the Subject means?
> >
> > At first, I took it to mean a comical expression of sarcasm because of an
> accident.
> >
> > Ironically, that?s not it.
> 
> It is an abbreviation of Antwort (answer) and was probably produced by
> some super smart software from Redmond.
> 

Yes, and it seem you can only change it by changing the language setting ?\_(?)_/?

> --
> embedded brains GmbH & Co. KG
> Herr Sebastian HUBER
> Dornierstr. 4
> 82178 Puchheim
> Germany
> email: sebastian.huber at embedded-brains.de
> phone: +49-89-18 94 741 - 16
> fax:   +49-89-18 94 741 - 08
> 
> Registergericht: Amtsgericht M?nchen
> Registernummer: HRB 157899
> Vertretungsberechtigte Gesch?ftsf?hrer: Peter Rasmussen, Thomas D?rfler
> Unsere Datenschutzerkl?rung finden Sie hier:
> https://embedded-brains.de/datenschutzerklaerung/
> _______________________________________________
> users mailing list
> users at rtems.org
> http://lists.rtems.org/mailman/listinfo/users

From miroslaw.dach at gmail.com  Wed Feb 14 18:22:52 2024
From: miroslaw.dach at gmail.com (Miroslaw Dach)
Date: Wed, 14 Feb 2024 10:22:52 -0800
Subject: EPICS and tftp file system
Message-ID: <CAPAFRJd1GQXNsn9yp7n4WjS6VMLP8aFVRrjWeEonP0vMKSMSRQ@mail.gmail.com>

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.txtst.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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20240214/e6414a06/attachment.htm>

From anj at anl.gov  Wed Feb 14 19:02:08 2024
From: anj at anl.gov (Johnson, Andrew N.)
Date: Wed, 14 Feb 2024 19:02:08 +0000
Subject: EPICS and tftp file system
In-Reply-To: <CAPAFRJd1GQXNsn9yp7n4WjS6VMLP8aFVRrjWeEonP0vMKSMSRQ@mail.gmail.com>
References: <CAPAFRJd1GQXNsn9yp7n4WjS6VMLP8aFVRrjWeEonP0vMKSMSRQ@mail.gmail.com>
Message-ID: <93104E08-D595-478F-8231-039F8A244E4E@anl.gov>

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>

From miroslaw.dach at gmail.com  Wed Feb 14 20:54:49 2024
From: miroslaw.dach at gmail.com (Miroslaw Dach)
Date: Wed, 14 Feb 2024 12:54:49 -0800
Subject: EPICS and tftp file system
In-Reply-To: <93104E08-D595-478F-8231-039F8A244E4E@anl.gov>
References: <CAPAFRJd1GQXNsn9yp7n4WjS6VMLP8aFVRrjWeEonP0vMKSMSRQ@mail.gmail.com>
 <93104E08-D595-478F-8231-039F8A244E4E@anl.gov>
Message-ID: <CAPAFRJfrZndBWbNqUT7zXS2a2zRbtXg0e3TT5HRarD3P=KmiTg@mail.gmail.com>

Hi Andrew,

Thanks for your e-mail.
>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.
I thought that setting the parameter RTEMS_FILESYSTEM_READ_WRITE in the
function call below would do the job:
  if (mount_and_make_target_path(devname,
                               "/TFTP/",
                               RTEMS_FILESYSTEM_TYPE_TFTPFS,
                               RTEMS_FILESYSTEM_READ_WRITE,
                               NULL))

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?

>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.
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:
https://epics.anl.gov/tech-talk/2022/msg00267.php

Best Regards
Mirek




?r., 14 lut 2024 o 11:02 Johnson, Andrew N. <anj at anl.gov> napisa?(a):

> 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/9f03120a/attachment-0001.htm>

From frank.kuehndel at embedded-brains.de  Thu Feb 15 10:25:59 2024
From: frank.kuehndel at embedded-brains.de (=?UTF-8?Q?Frank_K=C3=BChndel?=)
Date: Thu, 15 Feb 2024 11:25:59 +0100
Subject: EPICS and tftp file system
In-Reply-To: <CAPAFRJfrZndBWbNqUT7zXS2a2zRbtXg0e3TT5HRarD3P=KmiTg@mail.gmail.com>
References: <CAPAFRJd1GQXNsn9yp7n4WjS6VMLP8aFVRrjWeEonP0vMKSMSRQ@mail.gmail.com>
 <93104E08-D595-478F-8231-039F8A244E4E@anl.gov>
 <CAPAFRJfrZndBWbNqUT7zXS2a2zRbtXg0e3TT5HRarD3P=KmiTg@mail.gmail.com>
Message-ID: <354e9b53-a420-4bc7-b445-190afa556ee7@embedded-brains.de>

Hello Miroslaw,

On 2/14/24 21:54, Miroslaw Dach wrote:
> Thanks for your e-mail.
>> 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.
> I thought that setting the parameter RTEMS_FILESYSTEM_READ_WRITE in the
> function call below would do the job:
>    if (mount_and_make_target_path(devname,
>                                 "/TFTP/",
>                                 RTEMS_FILESYSTEM_TYPE_TFTPFS,
>                                 RTEMS_FILESYSTEM_READ_WRITE,
>                                 NULL))
> 
> 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?

I have no idea of EPICS. I just want to mention that RTEMS tftpfs is 
able to write to the server ? at least in current RTEMS 6:

https://docs.rtems.org/branches/master/filesystem/trivial_ftp.html

Greetings,
fk

-- 
embedded brains GmbH & Co. KG
Herr Frank K?HNDEL
Dornierstr. 4
82178 Puchheim
Germany
email: frank.kuehndel at embedded-brains.de
phone:  +49-89-18 94 741 - 23
mobile: +49-176-15 22 06 - 11

Registergericht: Amtsgericht M?nchen
Registernummer: HRA 117265
Vertretungsberechtigte Gesch?ftsf?hrer: Peter Rasmussen, Thomas D?rfler
Unsere Datenschutzerkl?rung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/

From rmderbes at gmail.com  Thu Feb 15 12:33:44 2024
From: rmderbes at gmail.com (rmd)
Date: Thu, 15 Feb 2024 09:33:44 -0300
Subject: =?UTF-8?B?UmU6IOKAnEFXOuKAnSA/?=
In-Reply-To: <646f70ef348743e2aecaade303733429@dlr.de>
References: <89B3B5B1-1546-42A7-B4B8-57A970F818BC@gmail.com>
 <8820fe4f-a339-45d7-a910-d95e0453e91f@embedded-brains.de>
 <646f70ef348743e2aecaade303733429@dlr.de>
Message-ID: <4599aad5-4e37-4e85-ab59-dcc7112c1bff@gmail.com>

It seems another pedantic expresion of fascism from redmond software...

Regards

RMD

On 2/1/24 05:51, Jan.Sommer at dlr.de wrote:
>
>> -----Original Message-----
>> From: users <users-bounces at rtems.org> On Behalf Of Sebastian Huber
>> Sent: Donnerstag, 1. Februar 2024 07:48
>> To: John Howard <echosoft.llc at gmail.com>; users at rtems.org
>> Subject: Re: ?AW:? ?
>>
>> On 31.01.24 18:20, John Howard wrote:
>>> Lost in translation.
>>>
>>> Anybody here know what ?AW:? in the Subject means?
>>>
>>> At first, I took it to mean a comical expression of sarcasm because of an
>> accident.
>>> Ironically, that?s not it.
>> It is an abbreviation of Antwort (answer) and was probably produced by
>> some super smart software from Redmond.
>>
> Yes, and it seem you can only change it by changing the language setting ?\_(?)_/?
>
>> --
>> embedded brains GmbH & Co. KG
>> Herr Sebastian HUBER
>> Dornierstr. 4
>> 82178 Puchheim
>> Germany
>> email: sebastian.huber at embedded-brains.de
>> phone: +49-89-18 94 741 - 16
>> fax:   +49-89-18 94 741 - 08
>>
>> Registergericht: Amtsgericht M?nchen
>> Registernummer: HRB 157899
>> Vertretungsberechtigte Gesch?ftsf?hrer: Peter Rasmussen, Thomas D?rfler
>> Unsere Datenschutzerkl?rung finden Sie hier:
>> https://embedded-brains.de/datenschutzerklaerung/
>> _______________________________________________
>> users mailing list
>> users at rtems.org
>> http://lists.rtems.org/mailman/listinfo/users
> _______________________________________________
> users mailing list
> users at rtems.org
> http://lists.rtems.org/mailman/listinfo/users

From miroslaw.dach at gmail.com  Thu Feb 15 19:15:24 2024
From: miroslaw.dach at gmail.com (Miroslaw Dach)
Date: Thu, 15 Feb 2024 11:15:24 -0800
Subject: EPICS and tftp file system
In-Reply-To: <354e9b53-a420-4bc7-b445-190afa556ee7@embedded-brains.de>
References: <CAPAFRJd1GQXNsn9yp7n4WjS6VMLP8aFVRrjWeEonP0vMKSMSRQ@mail.gmail.com>
 <93104E08-D595-478F-8231-039F8A244E4E@anl.gov>
 <CAPAFRJfrZndBWbNqUT7zXS2a2zRbtXg0e3TT5HRarD3P=KmiTg@mail.gmail.com>
 <354e9b53-a420-4bc7-b445-190afa556ee7@embedded-brains.de>
Message-ID: <CAPAFRJeaVx0gth+y8Law19+hTS=U7cgVaiuG-trExJo2eXSefA@mail.gmail.com>

Hi Frank,

Thank you for your feedback on that. It might be then the setup in EPICS.

Best Regards
Mirek


czw., 15 lut 2024 o 02:26 Frank K?hndel <frank.kuehndel at embedded-brains.de>
napisa?(a):

> Hello Miroslaw,
>
> On 2/14/24 21:54, Miroslaw Dach wrote:
> > Thanks for your e-mail.
> >> 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.
> > I thought that setting the parameter RTEMS_FILESYSTEM_READ_WRITE in the
> > function call below would do the job:
> >    if (mount_and_make_target_path(devname,
> >                                 "/TFTP/",
> >                                 RTEMS_FILESYSTEM_TYPE_TFTPFS,
> >                                 RTEMS_FILESYSTEM_READ_WRITE,
> >                                 NULL))
> >
> > 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?
>
> I have no idea of EPICS. I just want to mention that RTEMS tftpfs is
> able to write to the server ? at least in current RTEMS 6:
>
> https://docs.rtems.org/branches/master/filesystem/trivial_ftp.html
>
> Greetings,
> fk
>
> --
> embedded brains GmbH & Co. KG
> Herr Frank K?HNDEL
> Dornierstr. 4
> 82178 Puchheim
> Germany
> email: frank.kuehndel at embedded-brains.de
> phone:  +49-89-18 94 741 - 23
> mobile: +49-176-15 22 06 - 11
>
> Registergericht: Amtsgericht M?nchen
> Registernummer: HRA 117265
> Vertretungsberechtigte Gesch?ftsf?hrer: Peter Rasmussen, Thomas D?rfler
> Unsere Datenschutzerkl?rung finden Sie hier:
> https://embedded-brains.de/datenschutzerklaerung/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20240215/cb8be8fb/attachment.htm>

From mdavidsaver at gmail.com  Thu Feb 15 22:38:40 2024
From: mdavidsaver at gmail.com (Michael Davidsaver)
Date: Thu, 15 Feb 2024 14:38:40 -0800
Subject: EPICS and tftp file system
In-Reply-To: <CAPAFRJd1GQXNsn9yp7n4WjS6VMLP8aFVRrjWeEonP0vMKSMSRQ@mail.gmail.com>
References: <CAPAFRJd1GQXNsn9yp7n4WjS6VMLP8aFVRrjWeEonP0vMKSMSRQ@mail.gmail.com>
Message-ID: <80ab7c7c-bea2-420f-b80d-dbed5a3a66b7@gmail.com>

On 2/14/24 10:22, Miroslaw Dach wrote:
> Does anybody have any advice?

Hi Mirek,

Have you tried with a CLI TFTP client?

Since TFTP is generally seen as wildly insecure
these days, default distro. installs of TFTPd
tend to be restrictive.

cf. "man tftpd" and compare with your running
daemon.

https://linux.die.net/man/8/tftpd


From miroslaw.dach at gmail.com  Fri Feb 23 23:38:52 2024
From: miroslaw.dach at gmail.com (Miroslaw Dach)
Date: Fri, 23 Feb 2024 15:38:52 -0800
Subject: EPICS and tftp file system
In-Reply-To: <80ab7c7c-bea2-420f-b80d-dbed5a3a66b7@gmail.com>
References: <CAPAFRJd1GQXNsn9yp7n4WjS6VMLP8aFVRrjWeEonP0vMKSMSRQ@mail.gmail.com>
 <80ab7c7c-bea2-420f-b80d-dbed5a3a66b7@gmail.com>
Message-ID: <CAPAFRJfspOE-QL7LMqo_h95usjxB1QR3sviVG=qxEiBDvOydHQ@mail.gmail.com>

Hi Michael,

I tried to read and write to/from the tftp server using the command
line tftp on my linux computer and all of that works fine
so it looks to me to be an issue with the RTEMS/EPICS setup.

Best Regards
Mirek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20240223/2662083f/attachment.htm>