diff options
author | Ron Yorston <rmy@pobox.com> | 2023-08-31 12:33:54 +0100 |
---|---|---|
committer | Ron Yorston <rmy@pobox.com> | 2023-08-31 12:33:54 +0100 |
commit | f498ba612f707d80c4c49d0a4fb58fd5c7c1b960 (patch) | |
tree | 1a98f18b2ea68e7a07f383824c5e083d5e1c0640 | |
parent | 2af141a2c069c56d56f110414f600f3a38ad8617 (diff) | |
download | busybox-w32-f498ba612f707d80c4c49d0a4fb58fd5c7c1b960.tar.gz busybox-w32-f498ba612f707d80c4c49d0a4fb58fd5c7c1b960.tar.bz2 busybox-w32-f498ba612f707d80c4c49d0a4fb58fd5c7c1b960.zip |
Update README.md
-rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -29,7 +29,7 @@ Then just `make`. | |||
29 | * Relative to current root (drive or share): `/path` | 29 | * Relative to current root (drive or share): `/path` |
30 | * Relative to current directory of current root (drive or share): `path` | 30 | * Relative to current directory of current root (drive or share): `path` |
31 | - Handling of users, groups and permissions is totally bogus. The system only admits to knowing about the current user and employs various heuristics to synthesise uid, gid and permission values. | 31 | - Handling of users, groups and permissions is totally bogus. The system only admits to knowing about the current user and employs various heuristics to synthesise uid, gid and permission values. |
32 | - 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 | - Some crufty old Windows code (Windows XP, cmd.exe) doesn't like forward slashes in environment variables. The -X shell option prevents busybox-w32 from changing backslashes to forward slashes. If Windows programs don't run from the shell it's worth trying it. |
33 | - 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. | 33 | - 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. |
34 | - The system tries to detect the best way to handle the terminal being used. If this doesn't work you can try setting the environment variable `BB_TERMINAL_MODE=1` to force the use of literal ANSI escapes or `BB_TERMINAL_MODE=0` to emulate them using the Windows console API. | 34 | - The system tries to detect the best way to handle the terminal being used. If this doesn't work you can try setting the environment variable `BB_TERMINAL_MODE=1` to force the use of literal ANSI escapes or `BB_TERMINAL_MODE=0` to emulate them using the Windows console API. |
35 | - busybox-w32 prefers built-in applets to external programs when running commands. This preference can be overridden by setting the environment variable `BB_OVERRIDE_APPLETS` to a space-separated list of applet names. Thus, to use an external `make` in preference to the built-in applet set `BB_OVERRIDE_APPLETS="make"`. | 35 | - busybox-w32 prefers built-in applets to external programs when running commands. This preference can be overridden by setting the environment variable `BB_OVERRIDE_APPLETS` to a space-separated list of applet names. Thus, to use an external `make` in preference to the built-in applet set `BB_OVERRIDE_APPLETS="make"`. |