public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Niklaus Giger <Niklaus.Giger@netstal.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Antw: TFTP usage at Linux shell prompt
Date: Wed, 21 Nov 2007 09:02:26 +0100	[thread overview]
Message-ID: <4743F422.268B.006F.0@netstal.com> (raw)
In-Reply-To: 13871777.post@talk.nabble.com

After entering "busybox tftp" into google my first hit was
http://www.busybox.net/lists/busybox/2003-February/007972.html 
which describes the tftp options. and which gives this tip

# ./busybox tftp --help
BusyBox v0.61.pre (2003.02.04-12:10+0000) multi-call binary

Usage: tftp [OPTION]... HOST [PORT]

Transfers a file from/to a tftp server using "octet" mode.

Options:
        -l FILE Local FILE.
        -r FILE Remote FILE.
        -g      Get file.
        -p      Put file.



Please consider also looking at the busybox homepage http://www.busybox.net/

This commonly called RTFM (Read the fucking manual)

Best regards



>>> Verma<ubootusers@gmail.com> schrieb am 21.11.07 um 07:23 in Nachricht
<13871777.post@talk.nabble.com>:

> Hi,
> 
> I am using JFFS2 file system for running the Linux on incaip board and would
> like to download a file from another host using TFTP.The following are the
> various commands and the respective outputs I have obtained when trying to
> download the file.
> 
> 1.command:        "#tftp 192.168.0.215"
> 
> output message:
>         BusyBox v1.00 (2007.11.20-05:01+0000) multi-call binary
> 
>          Usage: tftp [OPTION]... HOST [PORT]
> 
> 2.command:  "# tftp -m binary  192.168.0.215"
> 
> output message:
>             "tftp: illegal option -- m
>             BusyBox v1.00 (2007.11.20-05:01+0000) multi-call binary"
> 
> 3.command: "tftp v  192.168.0.215"
> 
> output message:
>           
>               "BusyBox v1.00 (2007.11.20-05:01+0000) multi-call binary
> 
>                Usage: tftp [OPTION]... HOST [PORT]"
> 
> Is the format of the commands valid, what are the list of options that could
> be given under OPTION field.
> Kindly, give me some pointers to proceed in solving this issue.
> 
> Thank You,
> Verma.
> 
> 

      reply	other threads:[~2007-11-21  8:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-21  6:23 [U-Boot-Users] TFTP usage at Linux shell prompt Verma
2007-11-21  8:02 ` Niklaus Giger [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=4743F422.268B.006F.0@netstal.com \
    --to=niklaus.giger@netstal.com \
    --cc=u-boot@lists.denx.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