| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
and probably some things not properly tested
|
|
|
|
| |
interfaces. From Max Holtzberg
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
configured out of the build for small systems that need minimal scripting capability
|
|
|
|
| |
line as the 'then' and 'else' tokens. This allows, as an example, 'if true; then echo true; else echo false; fi' which is much more bash-like
|
| |
|
|
|
|
| |
forthcoming looping
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
buffer resources (callback structure) when the socket is closed
|
| |
|
|
|
|
| |
buffering
|
| |
|
| |
|
| |
|
|
|
|
| |
strings, command output, application program output, and environment varaible values.
|
| |
|
| |
|
| |
|
|
|
|
| |
multiple, semicolone separated commands on each line
|
| |
|
|
|
|
| |
is necessary. For now, just removed the dependency on DHCPC in the Kconfig file, but more thought is needed.
|
| |
|
| |
|
| |
|
| |
|
| |
|