Signed-off-by: Robert Karszniewicz <avoidr@xxxxxxxxx> --- README | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README b/README index d8077d21b..0a837b2de 100644 --- a/README +++ b/README @@ -114,7 +114,7 @@ in board/sandbox/env: # ./scripts/bareboxenv -s -p 0x10000 arch/sandbox/board/env env.bin -To get some files to play with you can generate a cramfs image: +To get some files to play with, you can generate a cramfs image: # mkcramfs somedir/ cramfs.bin The barebox image is a normal Linux executable, so it can be started @@ -133,14 +133,14 @@ given with '-i' will appear as /dev/fd[n]. If barebox finds a valid configuration sector on /dev/env0 it will load it to /env. It then executes /env/init if it exists. If you have -loaded the example environment barebox will show you a menu asking for +loaded the example environment, barebox will show you a menu asking for your settings. -If you have started barebox as root you will find a new tap device on your +If you have started barebox as root, you will find a new tap device on your host which you can configure using ifconfig. Once you configured bareboxs -network settings accordingly you can do a ping or tftpboot. +network settings accordingly, you can do a ping or tftpboot. -If you have mapped a cramfs image try mounting it with +If you have mapped a cramfs image, try mounting it with # mkdir /cram # mount /dev/fd0 cramfs /cram -- 2.28.0 _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox