Home
last modified time | relevance | path

Searched refs:to (Results 1 – 25 of 202) sorted by relevance

123456789

/busybox-1.35.0/docs/
Dunicode.txt3 There are several scenarios where we need to handle unicode
8 We want to correctly handle input of unicode characters.
12 But we also need to handle the following problematic moments:
14 * It is unreasonable to expect that output device supports
15 _any_ unicode chars. Perhaps we need to avoid printing
19 combining chars (especially trying to combine bad pairs:
22 * We need to account for the fact that unicode chars have
26 * Bidirectional handling. If user wants to echo a phrase
31 This case is a bit similar to "shell input", but unlike shell,
33 (try to load a random binary file...), and they need to preserve
[all …]
Dlogging_and_backgrounding.txt3 By default, bb_[p]error_msg[_and_die] messages go to stderr,
8 Busybox is trying to provide compatible behavior, thus if an applet
11 If utility normally logs to syslog, busybox applet should do
16 Some might like logging everything from daemons to syslog.
18 logging to stderr and no daemonization.
20 To help with that, busybox applets should have options to override
27 crond - auto-backgrounds unless -f, logs to syslog unless -d or -L.
28 option -d logs to stderr, -L FILE logs to FILE
30 dnsd - option -d makes it background and log to syslog
31 fakeidentd - inetd service. Auto-backgrounds and logs to syslog
[all …]
Dcontributing.txt4 This document describes what you need to do to contribute to Busybox, where
5 you can help, guidelines on testing, and how to submit a well-formed patch
6 that is more likely to be accepted.
15 So you want to contribute to Busybox, eh? Great, wonderful, glad you want to
17 you need to do:
23 This is a necessary first step. Please do not try to work with the last
28 For information on how to check out Busybox development tree, please look at the
37 No one is required to read the entire archives of the mailing list, but you
40 you're the first to discover a problem, post a message and let the rest of us
47 If you have a serious interest in Busybox, i.e., you are using it day-to-day or
[all …]
Dkeep_data_small.txt13 In order to keep busybox NOMMU and small-mem systems friendly
18 Small experiment to measure "parasitic" bbox memory consumption:
61 One example how to reduce global data usage is in
65 * to place decompressor state either in bss or in
75 (see the rest of the file to get the idea)
79 and then passed down to all subroutines which need to access 'globals'
85 In case you don't want to pass this additional parameter everywhere,
87 single global pointer (ptr_to_globals) to allocated storage.
89 In order to not duplicate ptr_to_globals in every applet, you can
96 and then declare that ptr_to_globals is a pointer to it:
[all …]
Dnofork_noexec.txt4 to dramatically speed up execution. It will be slow as hell if for every
6 have to _reimplement_ these commands internally.
13 Applet will be subject to NOFORK/NOEXEC tricks only if it is marked
16 In C, if you want to call a program and wait for it, use
27 BB_EXECVP(cmd, argv) will try to exec /proc/self/exe
34 shells will try to exec /proc/self/exe if command's name matches
53 * do not expect shared global variables/buffers to be in their
70 "run_nofork_applet" to find more users).
79 - xfuncs are okay. They are using special trick to return
80 to the caller applet instead of dying when they detect "x" condition.
[all …]
Difupdown_design.txt1 This document is meant to convince you to not use ifup/ifdown.
5 fashion" by design. It tries to do the job of shell script in C,
6 and this is invariably doomed to fail. You need ifup/ifdown
7 to be adaptable by local admins, and C is an extremely poor choice
10 We are doomed to have problems with ifup/ifdown. Just look as this code:
37 How the hell it is supposed to work reliably this way? Just imagine that
43 I seriously urge people to not use ifup/ifdown.
/busybox-1.35.0/shell/hush_test/hush-misc/
Dcontrol_char4.tests1 # (set argv0 to "SHELL" to avoid "/path/to/shell: blah" in error messages)
Dcontrol_char3.tests1 # (set argv0 to "SHELL" to avoid "/path/to/shell: blah" in error messages)
/busybox-1.35.0/shell/ash_test/ash-misc/
Dcontrol_char3.tests1 # (set argv0 to "SHELL" to avoid "/path/to/shell: blah" in error messages)
Dcontrol_char4.tests1 # (set argv0 to "SHELL" to avoid "/path/to/shell: blah" in error messages)
/busybox-1.35.0/examples/shutdown-1.0/
DREADME4 # just ask all processes to exit.
8 # (and also possibly shutdown) to e.g.
15 # shutdown spawns do_shutdown in new session, redirected to /dev/null,
20 # do_shutdown tries to switch to a VT console.
21 # Then, (only if -r) it spawns a hardshutdown child, to reboot
23 # Then it runs stop_tasks, writing to /var/log/reboot/YYYYMMDDhhmmss.log,
25 # Then it commands kernel to halt/reboot/poweroff, if requested.
/busybox-1.35.0/networking/ssl_helper/
DREADME6 * Run ssl_helper.sh to compile and link the helper
8 Usage: "ssl_helper -d <FILE_DESCRIPTOR>" where FILE_DESCRIPTOR is open to the peer.
13 Stdin will be SSL-encrypted and sent to FILE_DESCRIPTOR.
14 Data from FILE_DESCRIPTOR will be decrypted and sent to stdout.
16 The plan is to adapt it for wget https helper, and for ssl support in nc.
/busybox-1.35.0/
DLICENSE14 Everyone is permitted to copy and distribute verbatim copies
19 The licenses for most software are designed to take away your
20 freedom to share and change it. By contrast, the GNU General Public
21 License is intended to guarantee your freedom to share and change free
22 software--to make sure the software is free for all its users. This
23 General Public License applies to most of the Free Software
24 Foundation's software and to any other program whose authors commit to
26 the GNU Library General Public License instead.) You can apply it to
29 When we speak of free software, we are referring to freedom, not
30 price. Our General Public Licenses are designed to make sure that you
[all …]
DINSTALL4 The BusyBox build process is similar to the Linux kernel build:
17 The easy way to try out BusyBox for the first time, without having to install
18 it, is to enable all features and then use "standalone shell" mode with a
24 extra configuration to use. Then enable "standalone shell" feature:
31 # exit back to top level menu
34 # exit back to top level menu
37 # use these commands to modify .config directly:
43 Standalone shell mode causes busybox's built-in command shell to run
49 to be set appropriately, depending on whether or not /proc/self/exe is
51 to the location of your busybox binary, usually /bin/busybox.
[all …]
DTODO8 Stuff that needs to be done. This is organized by who plans to get around to
9 doing it eventually, but that doesn't mean they "own" the item. If you want to
10 do one of these bounce an email off the person it's listed under to see if they
11 have any suggestions how they plan to go about it, and to minimize conflicts
20 work all that well (especially not in a chroot environment), due to apps not
40 also allows us to consolidate redundant (or close) strings.
42 We probably don't want to be bloated with locale support. (Not unless we
43 can cleanly export it from our underlying C library without having to
51 --unicode option to loadkeys. That implies a real loadkeys/dumpkeys
52 implementation to replace loadkmap/dumpkmap. Plus messing with console font
[all …]
DConfig.in19 Many applet options have dedicated config options to (de)select them
23 Select this if you plan to use busybox on full-blown desktop machine
27 If you are preparing your build to be used on an embedded box
38 if you plan to run busybox on desktop.
66 Enable this if you want busybox applets to use the gnu --long-option
67 style, in addition to single character -a -b -c style options.
75 If you do not want to show any (helpful) usage message when
85 This will add a lot of text to the binary.
105 If you need to work with large files, enable this option.
116 of direct access to password database.
[all …]
/busybox-1.35.0/networking/ssl_helper-wolfssl/
DREADME9 to a wolfssl-3.9.8 subdirectory here.
16 to compile and link the helper
18 Usage: "ssl_helper -d FILE_DESCRIPTOR" where FILE_DESCRIPTOR is open to the peer.
23 Stdin will be SSL-encrypted and sent to FILE_DESCRIPTOR.
24 Data from FILE_DESCRIPTOR will be decrypted and sent to stdout.
/busybox-1.35.0/shell/ash_test/ash-redir/
Dredir_script.tests2 # Note: one of these fds is a directory opened to /proc/self/fd
3 # for globbing. It is unwanted, but I don't know how to filter it out.
17 # One of the fds is open to the script body
26 # One legit way to handle it is to move script fd. For example, if we see that fd 10 moved to fd 11:
30 # or we see that fd 3 moved to fd 10:
/busybox-1.35.0/shell/hush_test/hush-redir/
Dredir_script.tests2 # Note: one of these fds is a directory opened to /proc/self/fd
3 # for globbing. It is unwanted, but I don't know how to filter it out.
17 # One of the fds is open to the script body
26 # One legit way to handle it is to move script fd. For example, if we see that fd 10 moved to fd 11:
30 # or we see that fd 3 moved to fd 10:
/busybox-1.35.0/shell/
Dbrace.txt4 ated. This mechanism is similar to pathname expansion, but the file-
5 names generated need not exist. Patterns to be brace expanded take the
8 lowed by an optional postscript. The preamble is prefixed to each
10 to each resulting string, expanding left to right.
13 are not sorted; left to right order is preserved. For example,
18 sion expands to each number between x and y, inclusive. When charac-
19 ters are supplied, the expression expands to each character lexico-
24 acters special to other expansions are preserved in the result. It is
25 strictly textual. Bash does not apply any syntactic interpretation to
31 A { or , may be quoted with a backslash to prevent its being considered
[all …]
/busybox-1.35.0/shell/ash_test/ash-vars/
Dvar6.tests2 # (set argv0 to "SHELL" to avoid "/path/to/shell: blah" in error messages)
/busybox-1.35.0/shell/hush_test/hush-vars/
Dvar6.tests2 # (set argv0 to "SHELL" to avoid "/path/to/shell: blah" in error messages)
/busybox-1.35.0/examples/var_service/
DREADME_distro_proposal.txt3 I installed Void Linux, in order to see what do they have.
51 Here is a link to Void Linux's wiki:
69 the link to /run/runit/* is conceptually wrong, it requires packagers
70 to know that /etc/rc should not be mutable and thus they need to use
73 I think a good thing would be to require just one file: the "run" script.
77 would not need to know how a particular distro manages logs.
78 Whatever their daemons print to stdout/stderr, should be automagically logged
85 The original idea of services-as-directories belongs to D.J.Bernstein (djb),
86 and his project to implement it is daemontools: https://cr.yp.to/daemontools.html
114 runit's service monitor (runsvdir) sends SIGTERM to supervisors
[all …]
/busybox-1.35.0/libbb/
Dudp_io.c33 const struct sockaddr *to, in send_to_from() argument
39 return sendto(fd, buf, len, flags, to, tolen); in send_to_from()
57 return sendto(fd, buf, len, flags, to, tolen); in send_to_from()
68 msg.msg_name = (void *)(struct sockaddr *)to; /* or compiler will annoy us */ in send_to_from()
121 struct sockaddr *from, struct sockaddr *to, in recv_from_to() argument
125 (void)to; /* suppress "unused to" warning */ in recv_from_to()
155 # define to4 ((struct sockaddr_in*)to) in recv_from_to()
156 # define to6 ((struct sockaddr_in6*)to) in recv_from_to()
166 to->sa_family = AF_INET; in recv_from_to()
178 to->sa_family = AF_INET6; in recv_from_to()
/busybox-1.35.0/examples/bootfloppy/
Dbootfloppy.txt4 This document describes how to buid a boot floppy using the following
20 Detailed instructions on how to build Busybox, uClibc, or a working Linux
24 - Stock Busybox from CVS or a tarball will work with no modifications to
28 won't be able to mount it's root file system.
31 refer to the web pages and documentation for those individual programs.
44 - Set up the rootfs file we just created to be used as a loop device (may not
58 (you will probably need to be root to do this)
65 (chdir to uClibc directory)
70 (path to)loop/lib
74 (chdir to busybox directory)
[all …]

123456789