From f7996f3b700a22797565e9aa57e251e6e3ac1e4d Mon Sep 17 00:00:00 2001
From: Denis Vlasenko
- BusyBox also has a feature called the + BusyBox also has a feature called the "standalone shell", where the busybox shell runs any built-in applets before checking the command path. This feature is also enabled by "make allyesconfig", and to try it out run @@ -261,7 +261,7 @@ within each applet. More build coverage testing.
-
we maintain such a list on this site! @@ -941,7 +941,7 @@ text console scrolling...)
So will data always be read from the far end of a pipe at the same chunk sizes it was written in? Nope. Don't rely on that. For one -counterexample, see rfc 896 +counterexample, see rfc 896 for Nagle's algorithm, which waits a fraction of a second or so before sending out small amounts of data through a TCP/IP connection in case more data comes in that can be merged into the same packet. (In case you were @@ -1089,7 +1089,7 @@ aaronl :Aaron Lehmann beppu :John Beppu dwhedon :David Whedon erik :Erik Andersen -gfeldman :Gennady Feldman +gfeldman :Gennady Feldman jimg :Jim Gleason kraai :Matt Kraai markw :Mark Whitley diff --git a/docs/busybox.net/news.html b/docs/busybox.net/news.html index 5492d6767..cdffd48eb 100644 --- a/docs/busybox.net/news.html +++ b/docs/busybox.net/news.html @@ -28,7 +28,7 @@
Control-C
. Or have interactive applications
that don't behave right when sending SIGINT. Examples are emacs'es
that die on Control-g or shellscript statements that sometimes are
executed and sometimes not, apparently not determined by the user's
-intention.
+intention.
Now imagine the user hits C-c while a shellscript is executing its first program. The following programs receive SIGINT: program1 and -also the shell executing the script. program1 exits. +also the shell executing the script. program1 exits.
But what should the shell do? If we say that it is only the innermost's programs business to react on SIGINT, the shell will do @@ -351,7 +351,7 @@ that do not properly communicate the required information up to the calling program.
Unless a program messes with signal handling, the system does this -automatically. +automatically.
There are programs that want to exit on SIGINT, but they don't let the system do the automatic exit, because they want to do some @@ -425,7 +425,7 @@ Notes: special numeric value. People often assume this since the manuals for shells often list some return value for exactly this. But this is just a convention for your shell script. It does not work from one UNIX API -program to another. +program to another.
All that happens is that the shell sets the "$?" variable to a special numeric value for the convenience of your script, because your @@ -571,7 +571,7 @@ comments the scripts echo.