From a4fe6056f3921926cadfd7e81590a34c21693a3d Mon Sep 17 00:00:00 2001 From: Waldemar Brodkorb Date: Sat, 8 Jan 2022 19:28:09 +0100 Subject: busybox/hush: update to 1.35.0 --- package/busybox/config/miscutils/Config.in | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) (limited to 'package/busybox/config/miscutils') diff --git a/package/busybox/config/miscutils/Config.in b/package/busybox/config/miscutils/Config.in index 549042515..a236373ae 100644 --- a/package/busybox/config/miscutils/Config.in +++ b/package/busybox/config/miscutils/Config.in @@ -12,6 +12,12 @@ config BUSYBOX_ADJTIMEX help Adjtimex reads and optionally sets adjustment parameters for the Linux clock adjustment algorithm. +config BUSYBOX_ASCII + bool "ascii" + default y + help + Print ascii table. + config BUSYBOX_BBCONFIG bool "bbconfig (9.7 kb)" default n @@ -783,4 +789,19 @@ config BUSYBOX_WATCHDOG certain amount of time, the watchdog device assumes the system has hung, and will cause the hardware to reboot. +config BUSYBOX_FEATURE_WATCHDOG_OPEN_TWICE + bool "Open watchdog device twice, closing it gracefully in between" + depends on BUSYBOX_WATCHDOG + default n # this behavior was essentially a hack for a broken driver + help + When enabled, the watchdog device is opened and then immediately + magic-closed, before being opened a second time. This may be necessary + for some watchdog devices, but can cause spurious warnings in the + kernel log if the nowayout feature is enabled. If this workaround + is really needed for you machine to work properly, consider whether + it should be fixed in the kernel driver instead. Even when disabled, + the behaviour is easily emulated with a "printf 'V' > /dev/watchdog" + immediately before starting the busybox watchdog daemon. Say n unless + you know that you absolutely need this. + endmenu -- cgit v1.2.3