From 02fd709d4cde968b78bdf0a08aeb3c8c118cbef5 Mon Sep 17 00:00:00 2001 From: Ron Yorston Date: Sun, 7 Feb 2021 14:48:38 +0000 Subject: Update README --- README.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index f45e2cc4e..09a5d64a2 100644 --- a/README.md +++ b/README.md @@ -21,8 +21,11 @@ Then just `make`. ### Limitations - Use forward slashes in paths: Windows doesn't mind and the shell will be happier. - - Don't do wild things with Windows drive or UNC notation. - - 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. + - Windows paths are different from Unix: + * Absolute paths: `c:/path` or `//host/share` + * Relative to current directory of other drive: `c:path` + * Relative to current root (drive or share): `/path` + * Relative to current directory of current root (drive or share): `path` - 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. - 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. - 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. -- cgit v1.2.3-55-g6feb