{"id":119982,"date":"2024-09-29T09:43:00","date_gmt":"2024-09-29T07:43:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/reliz-minimalistichnogo-nabora-sistemnyh-utilit-busybox-1-37"},"modified":"2024-09-29T09:43:00","modified_gmt":"2024-09-29T07:43:00","slug":"reliz-minimalistichnogo-nabora-sistemnyh-utilit-busybox-1-37","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/reliz-minimalistichnogo-nabora-sistemnyh-utilit-busybox-1-37","title":{"rendered":"Release of the minimalist set of system utilities BusyBox 1.37","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
After almost two years of development, the release of the BusyBox 1.37 package has been presented, featuring a set of standard UNIX utilities packaged into a single executable file and optimized for minimal resource consumption, with a package size of less than 1 MB. The first release of the new 1.37 branch is positioned as unstable, with full stabilization expected in version 1.37.1, which is anticipated in a few months. The project code is distributed under the GPLv2 license. <\/p>\n
The modular nature of BusyBox allows for the creation of a single unified executable file containing an arbitrary set of utilities implemented in the package (each utility is available as a symbolic link to this file). The size, composition, and functionality of the utility collection can vary depending on the needs and capabilities of the embedded platform for which the build is being done. The package is self-sufficient, requiring only a few device files to be created in the \/dev directory and the preparation of configuration files for a working system on top of the Linux kernel when statically built with uClibc. Compared to the previous release 1.36, the memory consumption of the typical BusyBox 1.37 build increased by 1535 bytes (from 1022792 to 1024327 bytes). <\/p>\n
BusyBox is a key tool in fighting GPL violations in firmware. The Software Freedom Conservancy (SFC) and the Software Freedom Law Center (SFLC) have successfully pressured companies that do not provide access to the source code of GPL programs, both through litigation and by reaching out-of-court agreements on behalf of BusyBox developers. At the same time, the author of BusyBox strongly opposes such protection, believing that it undermines his business. <\/p>\n
Notable changes in BusyBox 1.37 include: <\/p>\n
\n
Added implementation of the getfattr utility to display extended file attributes.\n
Optional support for the BOOTP protocol has been implemented in udhcpd.\n
The hwclock utility now has the ability to output and set RTC (Real-Time Clock) parameters. For example, to read: 'hwclock --param-get bsm', and to change: 'hwclock -p bsm=1'.\n
The 'ip link' command now supports configuring CAN devices using the netlink interface ('ip link set type can').\n
The find utility has implemented the option '-ok command' to run a command with a user confirmation prompt for this operation.\n
Another batch of fixes for the ash and hush command shells has been included, aimed at improving compatibility with other shells. Support for autocompleting function names and aliases with the Tab key has been added. A built-in implementation of the 'false' command has been added to hush.\n
In awk, the flag '-E' has been implemented to read the script text from a file.\n
In the od utility, the option '-B' (an alias for '-t o2') has been implemented for outputting in octal 2-byte values.\n
In the time utility, the option '-f FMT' now allows character escaping using the sequences '\\escape' and '%%'.\n
The top utility has improved the display of large PID identifiers.\n
The readlink utility has added support for the separator '\u2013' and improved compatibility with the POSIX standard regarding the use of the '-n' option.\n
The start-stop-daemon command has added options '-O\/--output' (for output redirection) and '-d DIR' (to change the default directory).\n