busybox-w32/findutils, branch realpath

Merge branch 'busybox' into merge

2018-05-13T07:15:58+00:00

free: improve --help for type option

2018-04-24T08:13:45+00:00

Patch by Fred Friedrich. Signed-off-by: Denys Vlasenko

Merge branch 'busybox' into merge

2018-04-09T07:50:34+00:00

xargs: use bb_ask_y_confirmation_FILE() instead of homegrown copy

2018-04-07T13:23:10+00:00

function old new delta bb_ask_y_confirmation_FILE - 83 +83 inetd_main 2033 2043 +10 udhcp_send_kernel_packet 295 301 +6 rmescapes 306 310 +4 send_tree 353 355 +2 i2cdetect_main 674 672 -2 confirm_or_abort 43 38 -5 get_terminal_width_height 242 234 -8 bb_ask_y_confirmation 76 10 -66 xargs_main 823 755 -68 ------------------------------------------------------------------------------ (add/remove: 1/0 grow/shrink: 4/5 up/down: 105/-149) Total: -44 bytes Signed-off-by: Denys Vlasenko

Merge branch 'busybox' into merge

2018-04-02T08:24:14+00:00

grep: fix echo "aa" | busybox grep -F -w "a" (should not match)

2018-03-29T16:03:50+00:00

function old new delta grep_file 1461 1470 +9 Signed-off-by: Denys Vlasenko

Merge branch 'busybox' into merge

2017-11-03T14:16:08+00:00

grep: skip grepping symlinks to directories

2017-10-31T14:23:55+00:00

When grep is passed -r, recursive_action will treat any symlinks to directories not in the root as normal files, since it lstat's them and is therefore told they are not directories. However, file_action_grep will still try to fopen and read from them to see whether they match, which varies in behaviour across platforms. Linux will give EISDIR and thus grep will not find any matching lines, but FreeBSD will give the raw contents of the directory itself, which may match the given pattern. Also, if grep is passed -c, it will even print a count for these symlinks, even on Linux. Since this recursive_action behaviour is required for the correct functioning of other applets, such as tar, grep should handle this special case and skip any such symlinks. function old new delta file_action_grep 80 161 +81 Signed-off-by: James Clarke Signed-off-by: Denys Vlasenko

mingw: special-case xargs -P on Windows

2017-10-01T07:36:07+00:00

The patches to let xargs support parallel operations on Linux/Unix was contributed and accepted in upstream BusyBox. To benefit from this on Windows, we have to work quite a bit harder, was it is pretty hard to emulate the waitpid() semantics on Windows when pid is -1, i.e. when waiting for any child to exit. The problem is not so much accumulating the process handles of children we spawned (we could do that in our own spawn() implementation), but the fact that waitpid() returns exactly one pid even when multiple children have exited, retaining the rest of them for subsequent waitpid() calls. And on Linux/Unix, those pids are reserved even if the processes have exited, at least for a while, but not on Windows. And then there is the problem that BusyBox may have spawned *other* processes, too, not just the ones we care about in xargs -P. A much more elegant way is to add Windows-specific code to xargs.c that specifically handles the child processes spawned by xargs. So let's do this. Signed-off-by: Johannes Schindelin Signed-off-by: Ron Yorston

Merge branch 'busybox' into merge

2017-09-27T09:11:19+00:00