mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: yegorslists@googlemail.com
To: barebox@lists.infradead.org
Subject: [PATCH 1/2] Documentation/filesystems: add barebox prompt to the shell commands
Date: Mon, 29 Feb 2016 15:39:51 +0100	[thread overview]
Message-ID: <1456756792-21321-1-git-send-email-yegorslists@googlemail.com> (raw)

From: Yegor Yefremov <yegorslists@googlemail.com>

Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
---
 Documentation/filesystems/fat.rst   | 9 ++++-----
 Documentation/filesystems/nfs.rst   | 4 ++--
 Documentation/filesystems/ramfs.rst | 2 +-
 Documentation/filesystems/smhfs.rst | 2 +-
 Documentation/filesystems/tftp.rst  | 2 +-
 5 files changed, 9 insertions(+), 10 deletions(-)

diff --git a/Documentation/filesystems/fat.rst b/Documentation/filesystems/fat.rst
index 2138328..e39e34a 100644
--- a/Documentation/filesystems/fat.rst
+++ b/Documentation/filesystems/fat.rst
@@ -7,9 +7,8 @@ barebox supports FAT filesystems in both read and write modes with optional
 support for long filenames. A FAT filesystem can be mounted using the
 :ref:`command_mount` command::
 
-  mkdir /mnt
-  mount /dev/disk0.0 fat /mnt
-  ls /mnt
+  barebox:/ mkdir /mnt
+  barebox:/ mount /dev/disk0.0 fat /mnt
+  barebox:/ ls /mnt
   zImage barebox.bin
-  umount /mnt
-
+  barebox:/ umount /mnt
diff --git a/Documentation/filesystems/nfs.rst b/Documentation/filesystems/nfs.rst
index 4469ac1..ab51241 100644
--- a/Documentation/filesystems/nfs.rst
+++ b/Documentation/filesystems/nfs.rst
@@ -9,7 +9,7 @@ barebox has readonly support for NFSv3 in UDP mode.
 
 Example::
 
-   mount -t nfs 192.168.23.4:/home/user/nfsroot /mnt/nfs
+   barebox:/ mount -t nfs 192.168.23.4:/home/user/nfsroot /mnt/nfs
 
 The barebox NFS driver adds a ``linux.bootargs`` device parameter to the NFS device.
 This parameter holds a Linux kernel commandline snippet containing a suitable root=
@@ -17,7 +17,7 @@ option for booting from exactly that NFS share.
 
 Example::
 
-  devinfo nfs0
+  barebox:/ devinfo nfs0
   ...
   linux.bootargs: root=/dev/nfs nfsroot=192.168.23.4:/home/sha/nfsroot/generic-v7,v3,tcp
 
diff --git a/Documentation/filesystems/ramfs.rst b/Documentation/filesystems/ramfs.rst
index b7ece1a..d27f885 100644
--- a/Documentation/filesystems/ramfs.rst
+++ b/Documentation/filesystems/ramfs.rst
@@ -9,4 +9,4 @@ is ``ramfs``.
 
 Example::
 
-  mount none ramfs /somedir
+  barebox:/ mount none ramfs /somedir
diff --git a/Documentation/filesystems/smhfs.rst b/Documentation/filesystems/smhfs.rst
index 28de146..9e9993c 100644
--- a/Documentation/filesystems/smhfs.rst
+++ b/Documentation/filesystems/smhfs.rst
@@ -20,7 +20,7 @@ directory. Nevertheless, the files are there.
 
 Example::
 
-  mount -t smhfs /dev/null /mnt/smhfs
+  barebox:/ mount -t smhfs /dev/null /mnt/smhfs
 
 
 Host Side Setup
diff --git a/Documentation/filesystems/tftp.rst b/Documentation/filesystems/tftp.rst
index b5bb1b3..eeb3fcb 100644
--- a/Documentation/filesystems/tftp.rst
+++ b/Documentation/filesystems/tftp.rst
@@ -14,7 +14,7 @@ show an empty directory. Nevertheless, the files are there.
 
 Example::
 
-  mount -t tftp 192.168.23.4 /mnt/tftp
+  barebox:/ 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.1.4


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

             reply	other threads:[~2016-02-29 14:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 14:39 yegorslists [this message]
2016-02-29 14:39 ` [PATCH 2/2] Documentation/filesystems: pstore: fix formatting yegorslists
2016-03-01  8:46   ` 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=1456756792-21321-1-git-send-email-yegorslists@googlemail.com \
    --to=yegorslists@googlemail.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