diff options
| -rw-r--r-- | README.md | 7 |
1 files changed, 5 insertions, 2 deletions
| @@ -21,8 +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 | - Don't do wild things with Windows drive or UNC notation. | 24 | - Windows paths are different from Unix: |
| 25 | - 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. | 25 | * Absolute paths: `c:/path` or `//host/share` |
| 26 | * Relative to current directory of other drive: `c:path` | ||
| 27 | * Relative to current root (drive or share): `/path` | ||
| 28 | * Relative to current directory of current root (drive or share): `path` | ||
| 26 | - 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. |
| 27 | - 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. |
| 28 | - 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. |