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
[email protected]
http://lists.infradead.org/mailman/listinfo/barebox
