have any suggestions how they plan to go about it, and to minimize conflicts
between your work and theirs. But otherwise, all of these are fair game.
-Rob Landley <rob@landley.net>:
- Add BB_NOMMU to platform.h and migrate __uClinux__ tests to that.
- #if defined __UCLIBC__ && !defined __ARCH_USE_MMU__
+Rob Landley suggested these:
Add a libbb/platform.c
Implement fdprintf() for platforms that haven't got one.
Implement bb_realpath() that can handle NULL on non-glibc.
Cleanup bb_asprintf()
- Migrate calloc() and bb_calloc() occurrences to bb_xzalloc().
Remove obsolete _() wrapper crud for internationalization we don't do.
Figure out where we need utf8 support, and add it.
sh
- The command shell situation is a big mess. We have three or four different
+ The command shell situation is a big mess. We have three different
shells that don't really share any code, and the "standalone shell" doesn't
work all that well (especially not in a chroot environment), due to apps not
- being reentrant. I'm writing a new shell (bbsh) to unify the various
- shells and configurably add the minimal set of bash features people
- actually use. The hardest part is it has to configure down as small as
- lash while providing lash's features. The rest is easy in comparison.
- bzip2
- Compression-side support.
+ being reentrant.
+ lash is phased out. hush can be configured down to be nearly as small,
+ but less buggy :)
init
- General cleanup (should use ENABLE_FEATURE_INIT_SYSLOG and ENABLE_FEATURE_INIT_DEBUG).
- depmod
- busybox lacks a way to update module deps when running from firmware without the
- use of the depmod.pl (perl is to bloated for most embedded setups) and or orig
- modutils. The orig depmod is rather pointless to have to add to a firmware image
- in when we already have a insmod/rmmod and friends.
- Unify base64 handling.
- There's base64 encoding and decoding going on in:
- networking/wget.c:base64enc()
- coreutils/uudecode.c:read_base64()
- coreutils/uuencode.c:tbl_base64[]
- networking/httpd.c:decodeBase64()
- And probably elsewhere. That needs to be unified into libbb functions.
+ General cleanup (should use ENABLE_FEATURE_INIT_SYSLOG).
Do a SUSv3 audit
Look at the full Single Unix Specification version 3 (available online at
"http://www.opengroup.org/onlinepubs/009695399/nfindex.html") and
This one's open to everybody, but I'll wind up doing it...
-Bernhard Fischer <busybox@busybox.net> suggests to look at these:
+Bernhard Reutner-Fischer <busybox@busybox.net> suggests to look at these:
New debug options:
-Wlarger-than-127
Cleanup any big users
- -Wunused-parameter
- Facilitate applet PROTOTYPES to provide means for having applets that
- do a) not take any arguments b) need only one of argc or argv c) need
- both argc and argv. All of these three options should go for the most
- feature complete denominator.
Collate BUFSIZ IOBUF_SIZE MY_BUF_SIZE PIPE_PROGRESS_SIZE BUFSIZE PIPESIZE
make bb_common_bufsiz1 configurable, size wise.
make pipesize configurable, size wise.
As yet unclaimed:
-----
-find
- doesn't understand (), lots of susv3 stuff.
----
diff
Make sure we handle empty files properly:
And while we're at it, a new patch filename quoting format is apparently
coming soon: http://marc.theaimsgroup.com/?l=git&m=112927316408690&w=2
---
-ps / top
- Add support for both RSS and VSIZE rather than just one or the other.
- Or make it a build option.
----
-man
- It would be nice to have a man command. Not one that handles troff or
- anything, just one that can handle preformatted ascii man pages, possibly
- compressed. This could probably be a script in the extras directory that
- calls cat/zcat/bzcat | less
-
- (How doclifter might work into this is anybody's guess.)
----
ar
- Write support?
+ Write support!
---
stty / catv
stty's visible() function and catv's guts are identical. Merge them into
---
Text buffer support.
Several existing applets (sort, vi, less...) read
- a whole file into memory and act on it. There might be an opportunity
- for shared code in there that could be moved into libbb...
+ a whole file into memory and act on it. Use open_read_close().
---
Memory Allocation
We have a CONFIG_BUFFER mechanism that lets us select whether to do memory
FEATURE_CLEAN_UP
This is more an unresolved issue than a to-do item. More thought is needed.
- Normally we rely on exit() to free memory, close files, and unmap segments
+ Normally we rely on exit() to free memory, close files and unmap segments
for us. This makes most calls to free(), close(), and unmap() optional in
busybox applets that don't intend to run for very long, and optional stuff
can be omitted to save size.
---
use bb_perror_msg where appropriate: See
egrep "[^_]perror"
----
- Remove superfluous fmt occurances: e.g.
- fprintf(stderr, "%s: %s not found\n", "unalias", *argptr);
- -> fprintf(stderr, "unalias: %s not found\n", *argptr);
---
possible code duplication ingroup() and is_a_group_member()
---
Move __get_hz() to a better place and (re)use it in route.c, ash.c, msh.c
---
+ See grep -r strtod
+ Alot of duplication that wants cleanup.
+---
+ in_ether duplicated in network/{interface,ifconfig}.c
+---
+ unify progress_meter. wget, flash_eraseall, pipe_progress, fbsplash, setfiles.
Code cleanup:
Replace deprecated functions.
-bzero() -> memset()
----
-sigblock(), siggetmask(), sigsetmask(), sigmask() -> sigprocmask et al
---
vdprintf() -> similar sized functionality
---
projects / oweals / busybox.git / blobdiff