aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRon Yorston <rmy@pobox.com>2021-02-10 09:48:27 +0000
committerRon Yorston <rmy@pobox.com>2021-02-10 09:48:27 +0000
commit038bc6cc76f1099b05eba30da64ed7b639af0245 (patch)
tree9ba6b0944c68549d64d8086e4a79fcbd35115559
parent046b4a9b01c633e284bb211dd561a7a20c27962a (diff)
downloadbusybox-w32-038bc6cc76f1099b05eba30da64ed7b639af0245.tar.gz
busybox-w32-038bc6cc76f1099b05eba30da64ed7b639af0245.tar.bz2
busybox-w32-038bc6cc76f1099b05eba30da64ed7b639af0245.zip
Reformat README.md
-rw-r--r--README.md3
1 files changed, 1 insertions, 2 deletions
diff --git a/README.md b/README.md
index f01b9aa86..dac2d38ba 100644
--- a/README.md
+++ b/README.md
@@ -21,12 +21,11 @@ Then just `make`.
21### Limitations 21### Limitations
22 22
23 - Use forward slashes in paths: Windows doesn't mind and the shell will be happier. 23 - Use forward slashes in paths: Windows doesn't mind and the shell will be happier.
24 - Windows paths are different from Unix: 24 - Windows paths are different from Unix ([more detail](https://frippery.org/busybox/paths.html)):
25 * Absolute paths: `c:/path` or `//host/share` 25 * Absolute paths: `c:/path` or `//host/share`
26 * Relative to current directory of other drive: `c:path` 26 * Relative to current directory of other drive: `c:path`
27 * Relative to current root (drive or share): `/path` 27 * Relative to current root (drive or share): `/path`
28 * Relative to current directory of current root (drive or share): `path` 28 * Relative to current directory of current root (drive or share): `path`
29 For more details see this page on [pathnames](https://frippery.org/busybox/paths.html).
30 - Handling of users, groups and permissions is totally bogus. The system only admits to knowing about the current user and always returns the same hardcoded uid, gid and permission values. 29 - Handling of users, groups and permissions is totally bogus. The system only admits to knowing about the current user and always returns the same hardcoded uid, gid and permission values.
31 - Some crufty old Windows code (Windows XP, cmd.exe) doesn't like forward slashes in environment variables. The -X shell option (which must be the first argument) prevents busybox-w32 from changing backslashes to forward slashes. If Windows programs don't run from the shell it's worth trying it. 30 - Some crufty old Windows code (Windows XP, cmd.exe) doesn't like forward slashes in environment variables. The -X shell option (which must be the first argument) prevents busybox-w32 from changing backslashes to forward slashes. If Windows programs don't run from the shell it's worth trying it.
32 - If you want to install 32-bit BusyBox in a system directory on a 64-bit version of Windows you should put it in `C:\Windows\SysWOW64`, not `C:\Windows\System32` as you might expect. On 64-bit systems the latter is for 64-bit binaries. 31 - If you want to install 32-bit BusyBox in a system directory on a 64-bit version of Windows you should put it in `C:\Windows\SysWOW64`, not `C:\Windows\System32` as you might expect. On 64-bit systems the latter is for 64-bit binaries.