[OpenWrt-Devel] how to set busybox's some options now ?

[xinglp]

There's some usefull options for me, such as SAVEHISTORY,
REVERSE_SEARCH, WGET_TIMEOUT, netcat and TRACEROUTE6.
But the recent commit disabled the busybox configure memu. How to set
somethings for busybox now ?

My configure file's busybox part is below:
# CONFIG_BUSYBOX_CONFIG_ARPING is not set
# CONFIG_BUSYBOX_CONFIG_BUNZIP2 is not set
# CONFIG_BUSYBOX_CONFIG_CHROOT is not set
# CONFIG_BUSYBOX_CONFIG_FEATURE_CHECK_TAINTED_MODULE is not set
CONFIG_BUSYBOX_CONFIG_FEATURE_DD_THIRD_STATUS_LINE=y
# CONFIG_BUSYBOX_CONFIG_FEATURE_DEVPTS is not set
CONFIG_BUSYBOX_CONFIG_FEATURE_EDITING_SAVEHISTORY=y
# CONFIG_BUSYBOX_CONFIG_FEATURE_MOUNT_CIFS is not set
# CONFIG_BUSYBOX_CONFIG_FEATURE_PREFER_IPV4_ADDRESS is not set
CONFIG_BUSYBOX_CONFIG_FEATURE_REVERSE_SEARCH=y
# CONFIG_BUSYBOX_CONFIG_FEATURE_SHADOWPASSWDS is not set
CONFIG_BUSYBOX_CONFIG_FEATURE_STAT_FORMAT=y
CONFIG_BUSYBOX_CONFIG_FEATURE_TRACEROUTE_USE_ICMP=y
# CONFIG_BUSYBOX_CONFIG_FEATURE_WGET_STATUSBAR is not set
CONFIG_BUSYBOX_CONFIG_FEATURE_WGET_TIMEOUT=y
# CONFIG_BUSYBOX_CONFIG_FREE is not set
# CONFIG_BUSYBOX_CONFIG_FSYNC is not set
# CONFIG_BUSYBOX_CONFIG_HOSTID is not set
# CONFIG_BUSYBOX_CONFIG_HWCLOCK is not set
# CONFIG_BUSYBOX_CONFIG_INCLUDE_SUSv2 is not set
# CONFIG_BUSYBOX_CONFIG_LONG_OPTS is not set
# CONFIG_BUSYBOX_CONFIG_MKSWAP is not set
CONFIG_BUSYBOX_CONFIG_NC_110_COMPAT=y
CONFIG_BUSYBOX_CONFIG_NC_EXTRA=y
CONFIG_BUSYBOX_CONFIG_NC_SERVER=y
# CONFIG_BUSYBOX_CONFIG_PASSWD is not set
CONFIG_BUSYBOX_CONFIG_PKILL=y
CONFIG_BUSYBOX_CONFIG_PSCAN=y
CONFIG_BUSYBOX_CONFIG_PSTREE=y
# CONFIG_BUSYBOX_CONFIG_RMMOD is not set
# CONFIG_BUSYBOX_CONFIG_SHOW_USAGE is not set
CONFIG_BUSYBOX_CONFIG_STAT=y
# CONFIG_BUSYBOX_CONFIG_STRINGS is not set
# CONFIG_BUSYBOX_CONFIG_SWITCH_ROOT is not set
# CONFIG_BUSYBOX_CONFIG_TELNET is not set
# CONFIG_BUSYBOX_CONFIG_TELNETD is not set
CONFIG_BUSYBOX_CONFIG_TRACEROUTE6=y
# CONFIG_BUSYBOX_CONFIG_VERBOSE_RESOLUTION_ERRORS is not set

Thanks.

[Yousong Zhou]

Hi,

Post by xinglp
There's some usefull options for me, such as SAVEHISTORY,
REVERSE_SEARCH, WGET_TIMEOUT, netcat and TRACEROUTE6.
But the recent commit disabled the busybox configure memu. How to set
somethings for busybox now ?

The config for busybox can be overridden via `env/busybox-config'. See r39107.

Do a `make menuconfig' for busybox, then save the necessary part to
`env/busybox-config' should work.


yousong

[o***@couprie.net]

Hi yousong,

Can you give a example how to call menuconfig for busybox ?

Perry

Post by Yousong Zhou
Hi,

Post by xinglp
There's some usefull options for me, such as SAVEHISTORY,
REVERSE_SEARCH, WGET_TIMEOUT, netcat and TRACEROUTE6.
But the recent commit disabled the busybox configure memu. How to set
somethings for busybox now ?

The config for busybox can be overridden via `env/busybox-config'. See r39107.
Do a `make menuconfig' for busybox, then save the necessary part to
`env/busybox-config' should work.
yousong
_______________________________________________
openwrt-devel mailing list
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[Yousong Zhou]

Post by o***@couprie.net
Hi yousong,
Can you give a example how to call menuconfig for busybox ?

I am doing menuconfig for busybox in OpenWrt build environment in
which busybox tarball has already been extracted. Your situation may
vary. Busybox itself provide menuconfig just like those for
OpenWrt/Buildroot/Kernel.

$ make -C build_dir/target-mips_34kc_uClibc-0.9.33.2/busybox-1.19.4/
menuconfig

Does it deserve a "busybox_menuconfig" just like "kernel_menuconfig"?

[Martijn Zilverschoon]

I think it does, because that also saves a lot of questions in the
future (hopefully). Because I think a lot of people that build there
own custom openwrt firmware often also modify the busybox config.

Post by Yousong Zhou

Post by o***@couprie.net
Hi yousong,
Can you give a example how to call menuconfig for busybox ?

I am doing menuconfig for busybox in OpenWrt build environment in
which busybox tarball has already been extracted. Your situation may
vary. Busybox itself provide menuconfig just like those for
OpenWrt/Buildroot/Kernel.
$ make -C build_dir/target-mips_34kc_uClibc-0.9.33.2/busybox-1.19.4/
menuconfig
Does it deserve a "busybox_menuconfig" just like "kernel_menuconfig"?
_______________________________________________
openwrt-devel mailing list
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[Hannu Nyman]

Does it deserve a "busybox_menuconfig" just like "kernel_menuconfig"?

I think it does, because that also saves a lot of questions in the
future (hopefully). Because I think a lot of people that build there
own custom openwrt firmware often also modify the busybox config.

I was especially surprised that not only the system-critical config options
were removed, but also the "harmless" usual add-on tools & commands like
diff, traceroute6 etc. were removed at the same time.

I would prefer those add-ons to return to the main menuconfig for easier use,
and the options for more deep down system stuff could be left to a new
busybox_menuconfig.

The config for busybox can be overridden via `env/busybox-config'. See r39107.

Another method is to manually edit the new busybox default config at
package/utils/busybox/config/default
https://dev.openwrt.org/browser/trunk/package/utils/busybox/config/default

[e***@web.de]

Post by Yousong Zhou

Post by o***@couprie.net
Hi yousong,
Can you give a example how to call menuconfig for busybox ?

I am doing menuconfig for busybox in OpenWrt build environment in
which busybox tarball has already been extracted. Your situation may
vary. Busybox itself provide menuconfig just like those for
OpenWrt/Buildroot/Kernel.
$ make -C build_dir/target-mips_34kc_uClibc-0.9.33.2/busybox-1.19.4/
menuconfig
Does it deserve a "busybox_menuconfig" just like "kernel_menuconfig"?

there should be at least one graphical way. so either busybox's menu_config or at least the old options presumably missing currently in trunk's menu_config.

..ede

[Maxim Storchak]

Post by e***@web.de

Post by Yousong Zhou
Does it deserve a "busybox_menuconfig" just like "kernel_menuconfig"?

there should be at least one graphical way. so either busybox's menu_config or at least the old options presumably missing currently in trunk's menu_config.

Would the attached patch help?

If there is an old config around, env/busybox-config may be created with
sed:
sed -nre '/CONFIG_BUSYBOX_/s/CONFIG_BUSYBOX_//p' config.old >
env/busybox-config

[Maxim Storchak]

Post by Maxim Storchak

Post by e***@web.de

Post by Yousong Zhou
Does it deserve a "busybox_menuconfig" just like "kernel_menuconfig"?

there should be at least one graphical way. so either busybox's menu_config or at least the old options presumably missing currently in trunk's menu_config.

Would the attached patch help?
If there is an old config around, env/busybox-config may be created with
sed -nre '/CONFIG_BUSYBOX_/s/CONFIG_BUSYBOX_//p' config.old >
env/busybox-config

oops, I'm sorry, I've lost another part of the patch. Please see this one.

Signed-off-by: Maxim Storchak <***@gmail.com>

[Michael Heimpold]

Hi,

Post by xinglp
There's some usefull options for me, such as SAVEHISTORY,
REVERSE_SEARCH, WGET_TIMEOUT, netcat and TRACEROUTE6.
But the recent commit disabled the busybox configure memu. How to set
somethings for busybox now ?
...

and another question is: how to depend on a specific busybox option.
I used to depend in various (private) packages on several busybox options
and could so ensure that the relevant commands are available in the
firmware. Is there a way, which I don't see at the moment?

BR, mhei

[Felix Fietkau]

Post by Michael Heimpold
Hi,

Post by xinglp
There's some usefull options for me, such as SAVEHISTORY,
REVERSE_SEARCH, WGET_TIMEOUT, netcat and TRACEROUTE6.
But the recent commit disabled the busybox configure memu. How to set
somethings for busybox now ?
...

and another question is: how to depend on a specific busybox option.
I used to depend in various (private) packages on several busybox options
and could so ensure that the relevant commands are available in the
firmware. Is there a way, which I don't see at the moment?

With the commit that I just made (r39125), you can add extra symbols to
the Config.in file of your package, similar to how NFS mount support is
now handled.

- Felix

[o***@couprie.net]

Hi,

I have a private openwrt package with the folowing line:

select BUSYBOX_CONFIG_CHPASSWD

After the busybox change it is not selected anymore.

Perry

Post by Felix Fietkau

Post by Michael Heimpold
Hi,

Post by xinglp
There's some usefull options for me, such as SAVEHISTORY,
REVERSE_SEARCH, WGET_TIMEOUT, netcat and TRACEROUTE6.
But the recent commit disabled the busybox configure memu. How to set
somethings for busybox now ?
...

and another question is: how to depend on a specific busybox option.
I used to depend in various (private) packages on several busybox options
and could so ensure that the relevant commands are available in the
firmware. Is there a way, which I don't see at the moment?

With the commit that I just made (r39125), you can add extra symbols to
the Config.in file of your package, similar to how NFS mount support is
now handled.
- Felix
_______________________________________________
openwrt-devel mailing list
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel