mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Robert Schwebel <r.schwebel@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 2/4] Documentation: filesystems: tftp: bring in line with other filesystem docs
Date: Wed, 10 Feb 2016 11:07:35 +0100	[thread overview]
Message-ID: <1455098857-25339-2-git-send-email-r.schwebel@pengutronix.de> (raw)
In-Reply-To: <1455098857-25339-1-git-send-email-r.schwebel@pengutronix.de>

Clarify that this is about the TFTP filesystem implementation, in
contrast to the tftp command.

Signed-off-by: Robert Schwebel <r.schwebel@pengutronix.de>
---
 Documentation/filesystems/tftp.rst | 14 +++++++++-----
 1 file changed, 9 insertions(+), 5 deletions(-)

diff --git a/Documentation/filesystems/tftp.rst b/Documentation/filesystems/tftp.rst
index e0a1159..b5bb1b3 100644
--- a/Documentation/filesystems/tftp.rst
+++ b/Documentation/filesystems/tftp.rst
@@ -2,15 +2,19 @@
 
 .. _filesystems_tftp:
 
-TFTP support
-============
+TFTP filesystem
+===============
 
-barebox has read/write support for the Trivial File Transfer Protocol.
+barebox has read/write support for the Trivial File Transfer Protocol (TFTP,
+`RFC1350 <https://tools.ietf.org/html/rfc1350>`_).
 
 TFTP is not designed as a filesystem. It does not have support for listing
-directories. This means a :ref:`command_ls` to a TFTP-mounted path will show an empty
-directory. Nevertheless, the files are there.
+directories. This means a :ref:`ls <command_ls>` to a TFTP-mounted path will
+show an empty directory. Nevertheless, the files are there.
 
 Example::
 
   mount -t tftp 192.168.23.4 /mnt/tftp
+
+In addition to the TFTP filesystem implementation, barebox does also have a
+:ref:`tftp command <command_tftp>`.
-- 
2.7.0.rc3


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2016-02-10 10:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10 10:07 [PATCH 1/4] Documentation: user manual: clarify kconfig+kbuild Robert Schwebel
2016-02-10 10:07 ` Robert Schwebel [this message]
2016-02-10 10:07 ` [PATCH 3/4] Documentation: user manual: improve tftp description Robert Schwebel
2016-02-10 10:07 ` [PATCH 4/4] Documentation: networking: improve docs Robert Schwebel
2016-02-10 10:15   ` Steffen Trumtrar
2016-02-11 12:53     ` 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=1455098857-25339-2-git-send-email-r.schwebel@pengutronix.de \
    --to=r.schwebel@pengutronix.de \
    --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