From: Sascha Hauer <s.hauer@pengutronix.de>
To: Franz Forstmayr <f.forstmayr@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [BUG] TFTP: No access to subdirectories
Date: Fri, 25 May 2018 08:25:45 +0200 [thread overview]
Message-ID: <20180525062545.6n7yqry3lln35rsg@pengutronix.de> (raw)
In-Reply-To: <CAGKTrWLu-r7OOFRW-JsbOz64O0jOz0CvJjVvHWzr-UFtVkcntg@mail.gmail.com>
Hi Franz,
On Thu, May 24, 2018 at 09:26:18AM +0200, Franz Forstmayr wrote:
> Hi,
>
> I just saw this old thread and wanted to ask, if this one has been
> fixed already? I just ran into a similar/same problem using
> barebox-2018-04 from the phytec repository
> (https://git.phytec.de/barebox/log/?h=v2018.04.0-phy).
>
> When i want to boot net the first time, it fails the second time successes.
I have no idea. Normally it should work, though I would have to test on
that version. can you reproduce it with the 'cp' command rather than
doing a net boot? Also, which tftp server have you running?
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-05-25 6:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 7:26 Franz Forstmayr
2018-05-25 6:25 ` Sascha Hauer [this message]
2018-05-25 6:53 ` Franz Forstmayr
2018-05-25 9:06 ` Sascha Hauer
-- strict thread matches above, loose matches on Subject: below --
2017-09-03 8:49 Dennis Menschel
2017-09-03 12:45 ` Antony Pavlov
2017-09-03 18:28 ` Dennis Menschel
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=20180525062545.6n7yqry3lln35rsg@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=f.forstmayr@gmail.com \
/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