From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Toews, Dietrich" <Dietrich.Toews@heidelberg.com>, 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 14:45:00 +0200 [thread overview]
Message-ID: <20180910124500.t6bu6vjxdkukemxq@pengutronix.de> (raw)
In-Reply-To: <F272D9410BD38E429D604B94748C61547AB0D488@WIEMS02101.ceu.corp.heidelberg.com>
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 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2018-09-10 12:45 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 [this message]
2018-09-10 13:31 ` Toews, Dietrich
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=20180910124500.t6bu6vjxdkukemxq@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=Dietrich.Toews@heidelberg.com \
--cc=barebox@lists.infradead.org \
--cc=g@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