From 038bc6cc76f1099b05eba30da64ed7b639af0245 Mon Sep 17 00:00:00 2001 From: Ron Yorston Date: Wed, 10 Feb 2021 09:48:27 +0000 Subject: Reformat README.md --- README.md | 3 +-- 1 file changed, 1 insertion(+), 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`. ### Limitations - Use forward slashes in paths: Windows doesn't mind and the shell will be happier. - - Windows paths are different from Unix: + - Windows paths are different from Unix ([more detail](https://frippery.org/busybox/paths.html)): * 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` - For more details see this page on [pathnames](https://frippery.org/busybox/paths.html). - 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