From: "Toews, Dietrich" <Dietrich.Toews@heidelberg.com>
To: Sascha Hauer <s.hauer@pengutronix.de>,
"g@pengutronix.de" <g@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: RE: unable to upload new file to tftp server
Date: Mon, 10 Sep 2018 13:31:32 +0000 [thread overview]
Message-ID: <F272D9410BD38E429D604B94748C61547AB0D50C@WIEMS02101.ceu.corp.heidelberg.com> (raw)
In-Reply-To: <20180910124500.t6bu6vjxdkukemxq@pengutronix.de>
Hi, Sascha,
I did not see the changes in master.
So I made the same patch and it works.
Thank you!
Dietrich
-----Original Message-----
From: Sascha Hauer [mailto:s.hauer@pengutronix.de]
Sent: Monday, September 10, 2018 2:45 PM
To: Toews, Dietrich RD-P6.3.4; g@pengutronix.de
Cc: barebox@lists.infradead.org
Subject: Re: unable to upload new file to tftp server
Hi Dietrich,
On Mon, Sep 10, 2018 at 10:08:52AM +0000, Toews, Dietrich wrote:
> Hi,
>
> when I try to upload a new file from barebox to an tftp server I always get the error: "Function not implemented".
>
> When the file is existing on the server, there is no problem.
>
> Prerequisites:
> - mounted directory to an tftp-server
> - test: cp local.file /mnt/tftp-dir/remote.file
>
> Progress:
> - first step of cp is to get the "stat" of the file - the answer of the tftp-server is ENOENT.
> - then cp tries to open the file, but it does only add O_TRUNC when the file exists
> - tftp_do_open returns ENOSYS when O_TRUNC is not set
>
> So you can't upload a non-existing file, but in most cases one needs exactly that.
Could you retry with current master? There have been some changes
recently.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
________________________________
Confidentiality note:
The information in this email and any attachment may contain confidential and proprietary information of Heidelberger Druckmaschinen AG and/or its affiliates and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any review, reliance or distribution by others or forwarding without express permission is strictly prohibited and may cause liability. In case you have received this message due to an error in transmission, we kindly ask you to notify the sender immediately and to delete this email and any attachment from your system.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2018-09-10 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 10:08 Toews, Dietrich
2018-09-10 12:45 ` Sascha Hauer
2018-09-10 13:31 ` Toews, Dietrich [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F272D9410BD38E429D604B94748C61547AB0D50C@WIEMS02101.ceu.corp.heidelberg.com \
--to=dietrich.toews@heidelberg.com \
--cc=barebox@lists.infradead.org \
--cc=g@pengutronix.de \
--cc=s.hauer@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox