On Fri, 09 Nov 2018 18:10:33 +
Ron Yorston wrote:
> Add an option to allow the content of embedded scripts to be
> displayed.
>
> It's disabled by default. When enabled:
I'd enable it unconditionally when embedded scripts are enabled.
And i would much prefer to name the option --show.
Michael Conrad wrote:
>Anyone with gdb would be able to extract the table and then
>decompress it back to the original directory of scripts.
Or a script like this:
#
# Extract bzip2 encoded data embedded in the busybox binary.
#
# Such data is compressed with 'bzip -1' so the first few
On Fri, 9 Nov 2018 16:51 Michael Conrad On 11/7/2018 10:49 AM, Ron Yorston wrote:
>
> Kang-Che Sung wrote:
>
> Specifically, I think the current state of config ASH_EMBEDDED_SCRIPTS
> help text did not yet warn builders that the binary may be distributed **only
> when the embedding scripts are
On Sat, Nov 10, 2018 at 2:10 AM Ron Yorston wrote:
>
> Add an option to allow the content of embedded scripts to be
> displayed.
>
> It's disabled by default. When enabled:
>
> function old new delta
> run_applet_and_exit
Hi,
I'am speechless...
but we still need an option to colorize the output ;-)
Ciao,
Tito
On 09/11/18 19:10, Ron Yorston wrote:
Add an option to allow the content of embedded scripts to be
displayed.
It's disabled by default. When enabled:
function
Add an option to allow the content of embedded scripts to be
displayed.
It's disabled by default. When enabled:
function old new delta
run_applet_and_exit 728 801 +73
.rodata
Michael Conrad wrote:
>Maybe if
>busybox had an option to dump out the scripts it would help enforce the
>idea that the sources were being shipped. Wonder how many bytes that
>would require...
122, apparently.
$ make bloatcheck
function old new
On 11/7/2018 10:49 AM, Ron Yorston wrote:
Kang-Che Sung wrote:
Specifically, I think the current state of config ASH_EMBEDDED_SCRIPTS help
text did not yet warn builders that the binary may be distributed **only when
the embedding scripts are GPLv2-compatible**. Builder and distributors may
Kang-Che Sung wrote:
>Since we are introducing the feature of embedding scripts into BusyBox, and
>user may now include and build their custom scripts into the BusyBox binary, I
>think there's one thing we forgot to address when this binary would be
>distributed. That is: the license problem.
I
Since we are introducing the feature of embedding scripts into BusyBox, and
user may now include and build their custom scripts into the BusyBox binary, I
think there's one thing we forgot to address when this binary would be
distributed. That is: the license problem.
Specifically, I think the
10 matches
Mail list logo
