Thread: [Announce] Enhanced BusyBox package
View Single Post
iDont is offline iDont
2011-11-24 , 18:38
Posts: 268 | Thanked: 1,053 times | Joined on May 2010 @ The Netherlands
#166
Originally Posted by reinob View Post
@iDont,

I assume you enabled the option for dropping privs when not needed, right?
Yep, grep for SUID in debian/config/config.busybox

Code:
[sbox-FREMANTLE_ARMEL: ~] > cat busybox/busybox-power/debian/config/config.busybox | grep SUID
CONFIG_FEATURE_SUID=y
CONFIG_FEATURE_SUID_CONFIG=y
CONFIG_FEATURE_SUID_CONFIG_QUIET=y
Originally Posted by SeT View Post
hi))
In "ls" output russian characters shows as ????, how to fix it?
On default BusyBox all good
Upstream BusyBox has a feature to check what language you have set in your environment variables (CONFIG_FEATURE_CHECK_UNICODE_IN_ENV). It's a good thing to respect these variables, at least by default (i.e. why would you want application XYZ to disrespect your system-wide settings when the user hasn't specifically told the application to do so?). For that reason is this feature enabled in busybox-power, with the result that if your locale isn't (for example) en_EN.UTF8 instead of en_EN, you won't have Unicode support enabled. This is most likely the case on your device.

However, I'll disable CONFIG_FEATURE_CHECK_UNICODE_IN_ENV in the upcoming busybox-power build (see Update 3 in this post)

Originally Posted by ade View Post
IDon't,

I'm experiencing something that looks like some bug in busybox-power_1.19.3power2. But it is strange I have heard no one else about it.
Yesterday I noticed Python apps started losing their skin/buttons.

I traced it down to this:
For some reason, TMPDIR is not set (or unset) in the user shell (it is still set in the root shell).
Because it is not set, python starts looking in /tmp for the sapwood-engine entry (/tmp/sapwood-:0.0), but is is running in /var/tmp. First exporting TMPDIR to /var/tmp before starting solves it for that session.

When I reverted back to busybox-power_1.19.3power1, TMPDIR was set again. Upgraded to busybox-power_1.19.3power2 again, and TMPDIR was gone.
Setting the export in /etc/profile or ~/.profile does not work. The problem does not occur in the bash shell.

Edit: the issue is visable then a sh shell is opened in a existing shell. TMPDIR is not passed on to the next shell.
Thanks for reporting, launching sh from sh indeed doesn't carry TMPDIR over, I'm looking into it right now.

Update: for some reason the TMPDIR issue is caused by the SUID bit on /bin/busybox. Running "chmod u-s /bin/busybox" fixes the issue with the latest busybox-power. Looking into that now.

Update 2: looks like some upstream issue; on my notebook:
Code:
[dennis@i7-820qm ~]$ export TMPDIR=/tmp
[dennis@i7-820qm ~]$ busybox sh
$ echo $TMPDIR
/tmp
$ exit
[dennis@i7-820qm ~]$ sudo chmod u+s /bin/busybox
[dennis@i7-820qm ~]$ busybox sh
$ echo $TMPDIR

$ busybox | head -n1
BusyBox v1.19.2 (2011-10-16 17:27:24 UTC) multi-call binary.
Only $TMPDIR seems to be affected, $FOO does get carried over on my notebook.

Update 3: Busybox-power 1.19.3power3 has been pushed to the repositories.

It unsets the SUID bit on /bin/busybox as a temporary workaround until the TMPDIR issue has been fixed properly. At the moment it looks like the issue is an upstream bug. I'll report the bug at BusyBox' bugtracker in a day or so, I want to do some additional tests before submitting a report.
This also means that su, ping (and some other SUID-bit requiring applets) won't work as a non-root user anymore (which is also the case with the default BusyBox) until the TMPDIR issue has been resolved.

Lastly, CONFIG_FEATURE_CHECK_UNICODE_IN_ENV has been disabled in this new build. A while ago hxka asked me why CONFIG_FEATURE_CHECK_UNICODE_IN_ENV is turned on in busybox-power. I didn't want to disable for compatibility reasons. There appear to be zero issues however, except that Ctrl-Space will produce a question mark instead of a space when Unicode support is turned on (versus the stock BusyBox; BB-power with Unicode support turned off will print no character at all upon pressing Ctrl-Space).
Last edited by iDont; 2011-11-24 at 20:09. Reason: Reply to SeT's post & Update 3
 

The Following 15 Users Say Thank You to iDont For This Useful Post: