| /busybox-1.35.0/loginutils/ |
| D | README | 4 For serial lines, it means "should getty wait for Carrier Detect pin?"
16 ??? mgetty opens tty but does NOT lock it, then waits for input via
17 select/poll, and when input is available, it checks lock file.
18 If it exists, mgetty exits (it assumes someone else uses the line).
19 If no, it creates the file (lock the tty). Sounds like a good algorithm
27 agetty call vhangup() after tty is opened. (Then agetty opens it again,
28 since it probably vhangup'ed its own fd too).
31 before it execs login program. Minor things we do conditionally are:
35 is it useful?
39 fails in process group leader. The workaround is to run it as a child
[all …]
|
| /busybox-1.35.0/shell/hush_test/hush-signals/ |
| D | exit.tests | 9 # EXIT trap is disabled after it is triggered,
10 # it can not be "re-armed" like this:
24 # EXIT trap is disabled after it is triggered,
25 # it can not be "re-armed" like this:
|
| /busybox-1.35.0/examples/shutdown-1.0/ |
| D | README | 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,
24 # then it runs stop_storage.
25 # Then it commands kernel to halt/reboot/poweroff, if requested.
26 # Then it sleeps forever.
|
| /busybox-1.35.0/examples/var_service/ |
| D | README_distro_proposal.txt | 66 That's it from the POV of the packager.
68 This is pretty minimalistic, and yet, it is already distro-specific:
69 the link to /run/runit/* is conceptually wrong, it requires packagers
86 and his project to implement it is daemontools: https://cr.yp.to/daemontools.html
90 (busybox has it included)
105 It should start it not as a child or daemonized process, but by exec'ing it
109 In daemontools package, it is called "svscan". In runit, it is called
110 "runsvdir". In s6, it is called "s6-svscan".
112 If it dies, it restarts it. If service directory disappears,
113 service monitor will not be restarted if it dies.
[all …]
|
| /busybox-1.35.0/shell/hush_test/hush-parsing/ |
| D | groups_and_keywords2.tests | 4 # ^^^^^^ bash prints 1, but interactively it sets $? = 2
7 # This is an error, and it aborts in script
|
| /busybox-1.35.0/shell/ash_test/ash-parsing/ |
| D | groups_and_keywords2.tests | 4 # ^^^^^^ bash prints 1, but interactively it sets $? = 2
7 # This is an error, and it aborts in script
|
| /busybox-1.35.0/networking/ssl_helper/ |
| D | README | 4 * Build it: "make"
10 In bash, you can do it this way:
16 The plan is to adapt it for wget https helper, and for ssl support in nc.
|
| /busybox-1.35.0/shell/ash_test/ash-vars/ |
| D | var_leak.tests | 1 # cat is an external program, variable should not leak out of it.
7 # true is a regular builtin, variable should not leak out of it.
13 # exec is a special builtin. (bash does not do it)
|
| D | var_expand_in_redir.tests | 8 # ash handles it as if it is '$*' - we do the same
|
| /busybox-1.35.0/testsuite/ |
| D | README | 3 -v option will cause it to show expected outcomes as well. To only run the test
31 If the test case relies on a certain feature, it should include the string
32 "FEATURE: " followed by the name of the feature in a comment. If it is always
33 expected to fail, it should include the string "XFAIL" in a comment.
40 This program is free software; you can redistribute it and/or
41 modify it under the terms of the GNU General Public License
45 This program is distributed in the hope that it will be useful,
|
| /busybox-1.35.0/docs/ |
| D | smallint.txt | 10 index_in_str_array returns int. At best, compiler will use it as-is.
11 At worst, compiler will try to make sure that it is properly cast
15 gcc will keep it in register. And even if it *is* stored,
16 it is *stack* storage, which is cheap (unlike data/bss).
|
| D | ifupdown_design.txt | 4 The general problem with ifupdown is that it is "copulated in vertical
37 How the hell it is supposed to work reliably this way? Just imagine that
39 admin installs dhclient, but does NOT use it. ifdown will STOP WORKING,
40 just because it will see installed dhclient binary in e.g. /usr/bin/dhclient!
|
| D | contributing.txt | 47 If you have a serious interest in Busybox, i.e., you are using it day-to-day or
48 as part of an embedded project, it would be a good idea to join the mailing
60 put significant effort into it and is probably more familiar with it than
64 Before plunging ahead, it's a good idea to send a message to the mailing list
66 'foo' applet. Would this be useful? Is anyone else working on it?" You might
81 Before listing the areas where you _can_ help, it's worthwhile to mention the
118 When I execute Busybox 'date' it produces unexpected results.
152 format (more on this below), but we're a little more lenient when it comes to
172 If you want to add a new applet to Busybox, we'd love to see it. However,
175 guys accept applet 'foo' into Busybox if I were to write it?" If the answer is
[all …]
|
| D | style-guide.txt | 14 files by typing 'indent myfile.c myfile.h' and it will magically apply all the
41 This is everybody's favorite flame topic so let's get it out of the way right
56 \t * Note that it has multiple lines
81 While it extends the line a bit longer, the spaced version is more
83 excluding the spacing makes it more obvious that we are dealing with a
84 single term (even if it is a compound term) such as:
96 If an opening bracket starts a function, it should be on the
97 next line with no spacing before it. However, if a bracket follows an opening
98 control block, it should be on the same line with a single space (not a tab)
99 between it and the opening control block statement. Examples:
[all …]
|
| D | keep_data_small.txt | 9 On NOMMU it's probably bites the most, actually using real
64 /* This is somewhat complex-looking arrangement, but it allows
96 and then declare that ptr_to_globals is a pointer to it:
101 This helps gcc understand that it won't change, resulting in noticeably
102 smaller code. In order to assign it, use SET_PTR_TO_GLOBALS macro:
106 Typically it is done in <applet>_main(). Another variation is
122 earlier mechanism to reduce bss usage. Each applet can use it for
123 its needs. Library functions are prohibited from using it.
129 Be careful, though, and use it only if globals fit into bb_common_bufsiz1.
131 from one libc to another, you have to add compile-time check for it:
[all …]
|
| /busybox-1.35.0/shell/ash_test/ash-redir/ |
| D | redir_script.tests | 3 # for globbing. It is unwanted, but I don't know how to filter it out.
18 # Close it while executing something.
21 # Shell should not lose that fd. Did it?
26 # One legit way to handle it is to move script fd. For example, if we see that fd 10 moved to fd 11:
|
| D | redir5.tests | 3 # 1. bash does not redirect stdin to /dev/null if it is interactive.
4 # hush does it always (this is allowed by standards).
|
| /busybox-1.35.0/shell/hush_test/hush-redir/ |
| D | redir_script.tests | 3 # for globbing. It is unwanted, but I don't know how to filter it out.
18 # Close it while executing something.
21 # Shell should not lose that fd. Did it?
26 # One legit way to handle it is to move script fd. For example, if we see that fd 10 moved to fd 11:
|
| D | redir5.tests | 3 # 1. bash does not redirect stdin to /dev/null if it is interactive.
4 # hush does it always (this is allowed by standards).
|
| /busybox-1.35.0/applets/ |
| D | Kbuild.src | 47 # and is generated by it. But specifying only it can run
49 # We say that it also needs NUM_APPLETS.h
52 # and it can be executed twice (sequentially).
54 # and then if include/applet_tables.h is deleted, it won't be rebuilt.
|
| /busybox-1.35.0/shell/hush_test/hush-vars/ |
| D | var_expand_in_redir.tests | 8 # ash handles it as if it is '$*' - we do the same
|
| /busybox-1.35.0/ |
| D | TODO | 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
43 can cleanly export it from our underlying C library without having to
44 concern ourselves with it directly. Perhaps a few specific things like a
49 at it? (There's some infrastructure here we don't implement: The
53 loading. Is it worth it, or do we just say "use X"?)
58 utils (or simply with less political baggage), but without it being one big
73 code). This means it would need (at least) binutils, gcc, and make, or
90 Write a mkdep that doesn't segfault if there's a directory it doesn't
[all …]
|
| D | LICENSE | 15 of this license document, but changing it is not allowed.
20 freedom to share and change it. By contrast, the GNU General Public
25 using it. (Some other Free Software Foundation software is covered by
26 the GNU Library General Public License instead.) You can apply it to
32 this service if you wish), that you receive source code or can get it
33 if you want it, that you can change the software or use pieces of it
39 distribute copies of the software, or if you modify it.
61 program proprietary. To prevent this, we have made it clear that any
71 a notice placed by the copyright holder saying it may be distributed
75 that is to say, a work containing the Program or a portion of it,
[all …]
|
| /busybox-1.35.0/shell/hush_test/hush-quoting/ |
| D | bkslash_in_varexp.tests | 5 # ] can be in a set if it is the first char: []abc],
6 # dash can be in a set if it is first or last: [abc-],
|
| /busybox-1.35.0/shell/ash_test/ash-quoting/ |
| D | bkslash_in_varexp.tests | 5 # ] can be in a set if it is the first char: []abc],
6 # dash can be in a set if it is first or last: [abc-],
|