Lines Matching refs:and

11 have any suggestions how they plan to go about it, and to minimize conflicts
12 between your work and theirs.  But otherwise, all of these are fair game.
19     shells that don't really share any code, and the "standalone shell" doesn't
25     "http://www.opengroup.org/onlinepubs/009695399/nfindex.html") and
26     figure out which of our apps are compliant, and what we're missing that
30     exercises each command line option and the various corner cases.
48     internationalizing the text console when X11 and xterms are so much better
50     "unicode_start" and "unicode_stop" shell scripts need "vt-is-UTF8" and a
71     sed, shadow, sysklogd, sysvinit, tar, util-linux, and vim.  The resulting
73     code).  This means it would need (at least) binutils, gcc, and make, or
79     would be nice to be able to upgrade busybox to be able to replace bash and
87     shell, mdev, and switch_root.
92     lexx and yacc, doesn't make such a mess under include/config, etc.
95     Go through and turn all the global and static variables into structures,
96     and have all those structures be in a big union shared between processes,
98     sed.c and mdev.c for examples.
100   Go through bugs.busybox.net and close out all of that somehow.
121     file will be removed unless patch is conforming to POSIX and the
147   traversal code should be factored out, and the guts of each archiver could
148   be some setup code and a series of callbacks for "add this file",
149   "add this directory", "add this symlink" and so on.
151   This could clean up tar and zip, and make it cheaper to add cpio and ar
152   write support, and possibly even cheaply add things like mkisofs or
157   a whole file into memory and act on it.  Use open_read_close().
162   We need to audit our memory allocations and turn a lot of malloc/free calls
168   free for an alloca()), and this means that various cleanup loops that just
170   we can yank those #ifdefs too, and generally clean up the code.
175   Normally we rely on exit() to free memory, close files and unmap segments
176   for us.  This makes most calls to free(), close(), and unmap() optional in
177   busybox applets that don't intend to run for very long, and optional stuff
186   and sometimes reliably (bb_perror_msg_and_die() or show_usage()).  This
187   jumps out of the normal flow control and bypasses any cleanup code we
190   It's possible to add hooks to libbb functions like xmalloc() and xopen()
191   to add their entries to a linked list, which could be traversed and
207   Unfortunately, that needs linux/watchdog.h and that contains unfiltered
216   possible code duplication ingroup() and is_a_group_member()
218   Move __get_hz() to a better place and (re)use it in route.c, ash.c
231   tc/brctl seem like fairly large things to try and tackle in your timeframe,
232   and i think people have posted attempts in the past. Adding additional
237 * implement POSIX utilities and audit them for POSIX conformance. then
243   and the complete list of all utilities that POSIX covers: