diff options
author | Ron Yorston <rmy@pobox.com> | 2015-06-16 21:17:03 +0100 |
---|---|---|
committer | Ron Yorston <rmy@pobox.com> | 2015-06-16 21:17:03 +0100 |
commit | 7c74f6f439591fbbfc4ade6ca989b11e087ccd1e (patch) | |
tree | 691ef60842df90118a11d61d927bdbc2727a55b7 | |
parent | 0ccf7a03aa45889993716581d675616db633ed33 (diff) | |
download | busybox-w32-7c74f6f439591fbbfc4ade6ca989b11e087ccd1e.tar.gz busybox-w32-7c74f6f439591fbbfc4ade6ca989b11e087ccd1e.tar.bz2 busybox-w32-7c74f6f439591fbbfc4ade6ca989b11e087ccd1e.zip |
Update README.md
-rw-r--r-- | README.md | 3 |
1 files changed, 2 insertions, 1 deletions
@@ -18,4 +18,5 @@ Then just `make`. | |||
18 | - Don't do wild things with Windows drive or UNC notation. | 18 | - Don't do wild things with Windows drive or UNC notation. |
19 | - Wildcard expansion is disabled by default, though it can be turned on at compile time. This only affects command line arguments to the binary: the BusyBox shell has full support for wildcards. | 19 | - Wildcard expansion is disabled by default, though it can be turned on at compile time. This only affects command line arguments to the binary: the BusyBox shell has full support for wildcards. |
20 | - 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. | 20 | - 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. |
21 | - Windows XP and Windows Server 2003 don't seem to like how busybox-w32 handles environment variables. The -X shell option (which must be the first argument) might help. | 21 | - Windows XP and Windows Server 2003 sometimes have trouble with forward slashes in environment variables. The -X shell option (which must be the first argument) prevents busybox-w32 from changing backslashes to forward slashes. |
22 | - Currently only 32-bit builds of BusyBox work. 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`. On 64-bit systems the latter is for 64-bit binaries. | ||