From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: "Toews, Dietrich" <Dietrich.Toews@heidelberg.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: PATCH added tftp port to fsoptions
Date: Mon, 6 Aug 2018 20:40:19 +0200 [thread overview]
Message-ID: <20180806184019.od66awd55aqxazio@pengutronix.de> (raw)
In-Reply-To: <F272D9410BD38E429D604B94748C61547AB08F97@WIEMS02101.ceu.corp.heidelberg.com>
On Fri, Aug 03, 2018 at 12:10:34PM +0000, Toews, Dietrich wrote:
> Hi,
>
> that can be a way, but then it is not possible to connect to different servers, when they have different ports.
> e.g. one server for large files, one (intelligent) server for script-files
>
> Why different ports? - For testing it is very nice to have all the servers on one machine.
>
> Dietrich
>
> -----Original Message-----
> Hi,
>
> Am 03.08.2018 um 13:07 schrieb Toews, Dietrich:
> > Hi all,
> >
> > we are using barebox for a while now, but we need different tftp-server with different ports.
> > Here a proposition for a patch, if someone else needs it also.
> >
> > Usage: tftp -o port=1234 ....
>
> Good point. I assume, barebox way, would be to make it:
> global.net.tftp_port
> nv.net.tftp_port
> nv.dev.<devname>.tftp_port
I'd say
nv.net.server.tftp_port=1234
and only use that for the default mount to /mnt/tftp and otherwise keep
it as a mount option.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2018-08-06 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 11:07 Toews, Dietrich
2018-08-03 11:34 ` Oleksij Rempel
2018-08-03 12:10 ` Toews, Dietrich
2018-08-06 18:40 ` Uwe Kleine-König [this message]
2018-08-08 8:15 ` Sascha Hauer
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=20180806184019.od66awd55aqxazio@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=Dietrich.Toews@heidelberg.com \
--cc=barebox@lists.infradead.org \
/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