brgl/busybox

The Swiss Army Knife of Embedded Linux - private tree

busybox's Issues

sed can’t handle emoji characters

#!/bin/sh
emoji="\U1f300-\U1f5ff\U1f900-\U1f9ff\U1f600-\U1f64f\U1f680-\U1f6ff\U2600-\U26ff\U2700-\U27bf\U1f1e6-\U1f1ff\U1f191-\U1f251\U1f004\U1f0cf\U1f170-\U1f171\U1f17e-\U1f17f\U1f18e\U3030\U2b50\U2b55\U2934-\U2935\U2b05-\U2b07\U2b1b-\U2b1c\U3297\U3299\U303d\U00a9\U00ae\U2122\U23f3\U24c2\U23e9-\U23ef\U25b6\U23f8-\U23fa"
sample="This 🍒 is ⭐ a 🐢 line 🤮 of 😃 emoji ✈"
echo $sample
echo $sample | LC_ALL=UTF-8 sed -e "s/[$(printf $emoji)]//g"

The preceding script can obtain normal execution results on other Linux operating systems (such as centos). However, if the script is executed on OpenWRT, an error message is displayed sed: bad regex Invalid character range or the correct result cannot be obtained after execution. Attempts were made to change the sed version to 4.8 but the problem persisted. Is this bash or is the system environment incomplete?

Attempts were made to change the sed version to 4.8 but the problem persisted
emoji="\U1f300-\U1f5ff" Trying to shorten emoji also works on centos, not openwrt

Unzip does not retain timestamps

The normal unzip behavior is to retain the timestamps and permissions of original compressed data. From testing, it looks like busybox version does neither.

help wanted: I want to get custom ENV variable in mdev

Hi, can you help me ?
I want to match MY_DEVICE_ID and then to exec some script,
example in /etc/mdev.conf
$MY_DEVICE_ID=201 root:root 660 @/bin/sh mount.sh
But, it is not good.
when I use ACTION, it is okay,
$ACTION=add root:root 660 @/bin/sh mount.sh
that is good
I know the ACTION is system ENV variable, so, what different with them?
Is the mdev not to do any thing when receiving custom ENV variable?

Look forward to your reply,
thank you