A mirror of https://github.com/rmyorston/busybox-w32.git https://git.lua4.win/busybox-w32/atom?h=1_00_pre4 2003-11-25T20:45:38+00:00 2003-11-25T20:45:38+00:00 Glenn L McGrath bug1@ihug.co.nz 2003-11-25T20:45:38+00:00 urn:sha1:4ddddd180eaa7a1f4b2071c37425d99c3ef8040d 2003-11-14T21:01:26+00:00 Glenn L McGrath bug1@ihug.co.nz 2003-11-14T21:01:26+00:00 urn:sha1:5c2c8eca4a175de7c73d3fbeb4c68817c6fd96d1 2003-10-22T10:56:47+00:00 Eric Andersen andersen@codepoet.org 2003-10-22T10:56:47+00:00 urn:sha1:a48b0a3af71958c1cea6389893371664a47b1a39 Stephane, >Using busybox+uclibc, crond syslog messages look like: > >Oct 9 09:04:46 soekris cron.notice crond[347]: ^Icrond 2.3.2 dillon, >started, log level 8 Thanks for testing. >The attached patch corrects the problem. Your patch is not correct. Correct patch attached. Also. Last patch have - add "Broken pipe" message to ash.c - busybox ash synced with dash_0.4.18 --w vodz 2003-10-22T09:58:56+00:00 Eric Andersen andersen@codepoet.org 2003-10-22T09:58:56+00:00 urn:sha1:88c916bdec7d444198f067529637b4a616ad3efe the busybox menuconfig triggered my "inacceptable number of spelling mistakes" upper level, so I decided to make a patch ;-) I also improved some wording to describe some things in a better way. Many thanks for an incredible piece of software! Andreas Mohr, random OSS developer 2003-09-17T00:22:26+00:00 Glenn L McGrath bug1@ihug.co.nz 2003-09-17T00:22:26+00:00 urn:sha1:d3612178b71b5c7d66252933c3e5a5980887c4ca The construct certain vintages of GCC (the one I have trouble with is 3.2.3) have trouble with looks like the following: static struct st a; static struct st *p = &a; struct st { int foo; }; static void init(void) { a.foo = 0; } The problem disappears if we move the struct declaration up to let the compiler know the shape of the struct before the first definition uses it, like this: struct st { int foo; }; /* this has been moved up */ static struct st a; static struct st *p = &a; static void init(void) { a.foo = 0; } 2003-09-15T14:42:39+00:00 Glenn L McGrath bug1@ihug.co.nz 2003-09-15T14:42:39+00:00 urn:sha1:a3822de23e8d2b1c173eab6925676de54c38b6f2 "If the shell is compiled with -DJOBS, this is all fine -- find wasn't stopped (it was killed), so it correctly uses WTERMSIG instead of WSTOPSIG. However, if the shell _isn't_ compiled with -DJOBS (which it isn't in d-i), only WSTOPSIG is used, which extracts the high byte instead of the low byte from the status code. Since the status code is 13 (SIGPIPE), "st" suddenly gets the value 0, which is equivalent to SIGEXIT. Thus, ash prints out "EXIT" on find's exit." 2003-09-15T12:00:19+00:00 Glenn L McGrath bug1@ihug.co.nz 2003-09-15T12:00:19+00:00 urn:sha1:47e5ca1ecb2a86b29c8a52ee3ed276d8b27147cf unless it had #!/bin/sh in the first line "It correctly locates the script, tries to execute it via execve which fails. After that it tries to hand it over to /bin/sh which fails too, since ash - neither provides the absolute pathname to /bin/sh - nor tries to lookup the script via PATH if called as "sh script" " 2003-09-15T08:33:45+00:00 Eric Andersen andersen@codepoet.org 2003-09-15T08:33:45+00:00 urn:sha1:8efe967018dd79aacfe3ca1e2583f115d744e466 to ensure proper fallback behavior on, i.e. serial consoles. -Erik 2003-09-12T04:49:21+00:00 Eric Andersen andersen@codepoet.org 2003-09-12T04:49:21+00:00 urn:sha1:f57a614db9db951df798d51351d1c64603ded186 on CONFIG_FEATURE_SH_STANDALONE_SHELL. 2003-09-02T02:36:18+00:00 Glenn L McGrath bug1@ihug.co.nz 2003-09-02T02:36:18+00:00 urn:sha1:dc4e75ef7ca135c836d22e380847672cf5b3773b constant. Vodz last_patch_107