[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: six patches from tinycore linux
From:       Denys Vlasenko <vda.linux () googlemail ! com>
Date:       2021-08-20 23:02:20
Message-ID: CAK1hOcOO=rM99VmvuBU6XCVms1=Tz-WwKXTZpFyywY_cdG1Svw () mail ! gmail ! com
[Download RAW message or body]

On Tue, Aug 10, 2021 at 3:02 PM Roberto A. Foglietta
<roberto.foglietta@gmail.com> wrote:
>
> Hi all,
>
>  At this address you can find six patches used by tinycore linux.
>  It might be possible that they have been submitted here yet, or not.
>  Otherwise, it worths to be evaluated
>
>  http://tinycorelinux.net/12.x/x86/release/src/busybox/
>
>  I inserted here their names:
>
> busybox-1.27.1-wget-make-default-timeout-configurable.patch

wget has an option to change the default, so why?
(A solution working to affect wget's inside scripts
would be an envvar instead of an option, but upstream
wget has no such thing)

> busybox-1.29.3_root_path.patch

 /* allow default system PATH to be extended via CFLAGS */
 #ifndef BB_ADDITIONAL_PATH
-#define BB_ADDITIONAL_PATH ""
+#define BB_ADDITIONAL_PATH ":/usr/local/bin"

Comment even says why this is not necessary (just set it in .config's CFLAGS).

> busybox-1.33.0_modprobe.patch

Anti-future-proofing patch: when kernel would learn how to finit_module(fd)
a gzipped module in addition to uncompressed ones, the patch would actually
make bbox LESS useful than it is now.

> busybox-1.33.0_skip-loop-control.patch

why?

> busybox-1.33.0_tc_depmod.patch

Might be a good idea, anyone has an explanation *why* depmod
has to follow symlinks? (IOW: bug report with a bit more info,
please)
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]