Reply
Thread Tools
Posts: 268 | Thanked: 1,053 times | Joined on May 2010 @ The Netherlands
#41
Originally Posted by Mentalist Traceur View Post
Meanwhile, I see busybox-power got a new update today. However, it does still list "busybox" as its dependency when you view it in the app manager. Was this intentional?
The dependency is removed; this seems to be a problem of HAM. You can see in the package's package instance page that busybox is not listed as a dependency anymore. I honestly wouldn't know why HAM is still listing it on your device.

Could you check if you get the same output as me when running the following command:
Code:
Nokia-N900:~# apt-cache depends busybox-power
busybox-power
  Depends: libc6
Originally Posted by Mentalist Traceur View Post
(Also, I'm going to be selfish and request loadkeys with the -b flag supported by added in - although, honestly, I'm making that a very tentative request, because I know if you keep adding stuff it'll just keep inflating the busybox binary, adding bloat that most people wouldn't want or need). I just cannot for the life of me find a precompiled armel binary of the loadkeys command that actually supports the -b flag.
Busybox hasn't got a loadkeys applet as far as I know. There has been a recent discussion regarding a similar this topic on BusyBox' mailing-list though. This reply suggests creating a loadkeys applet for BusyBox, but nobody has started working on it, at least as far as I can see (no commits regarding the applet have been made in the project's GIT repository).

By the way, I don't mind adding even more features to busybox-power; a heck of a lot has already been enabled (including relatively 'heavy' applets like httpd etcetera) and the binary grew by just under 400KiB compared to the original binary. This increase in size even includes the ~3 years of updates to BusyBox' source code since the old version used by default in Maemo. I don't think there is even that much more to enable

Last edited by iDont; 2011-05-20 at 08:56.
 

The Following 2 Users Say Thank You to iDont For This Useful Post:
Posts: 48 | Thanked: 32 times | Joined on Dec 2010 @ Russia, Moscow
#42
Originally Posted by iDont View Post
I could always write a patch to make ps accept all options again if it won't get fixed. For now, I'll leave this untouched. Installation and removal of Fennec should work fine nonetheless.
I've noticed that several packages (and handmade patches from this forum users) depend on the old way the ps command works, not only fennec.

Currently I'm using the procps package which accepts "ps a" style and gives a much nicer "top" output
 
ndi's Avatar
Posts: 2,050 | Thanked: 1,425 times | Joined on Dec 2009 @ Bucharest
#43
Hi.

Installed BusyBox, seemed OK, but broke a few things. Not sure which broke what, but I'll recount my experience:

Installed, fiddled with it (works fine), rebooted phone.

Phone would not reboot. Entered 5-dot animation, then played the video, then screen went blank. Not locked, but black, can-see-backlight-very-dark-gray-blue. Locking and unlocking the screen revealed the phone is in 5-dot animation, just refused to draw it.

Screen clicks, keys click, lock and unlock works, slide-lock works, but 5-dot never finishes.

Tried to use Backup Menu to restore, it didn't work. It started, then said "Chrooting ..." that usually is so fast I can't see, but it never finished chroot so hung.

Tried stock kernel to no avail.

Had to reflash and revert to an old image (3 weeks). Kind of a bummer.

Any ideas? Except "try again".
__________________
N900 dead and Nokia no longer replaces them. Thanks for all the fish.

Keep the forums clean: use "Thanks" button instead of the thank you post.
 
Posts: 856 | Thanked: 1,681 times | Joined on Apr 2010 @ Aleppo ,Syria
#44
There seems to be a problem with
ps
i have noticed it while installing fennec6 and
airmon-ng start wlan0 (it uses ps -A)

so ps -A

showes


~ $ ps -A
ps: invalid option -- A
BusyBox v1.18.4 (Debian 1.18.4power4) multi-call binary.

Usage: ps

Show list of processes

Options:
w Wide output

~ $


that means ps is not like the old one
How to fix this ?
 
Posts: 856 | Thanked: 1,681 times | Joined on Apr 2010 @ Aleppo ,Syria
#45
Originally Posted by ndi View Post
Hi.

Installed BusyBox, seemed OK, but broke a few things. Not sure which broke what, but I'll recount my experience:

Installed, fiddled with it (works fine), rebooted phone.

Phone would not reboot. Entered 5-dot animation, then played the video, then screen went blank. Not locked, but black, can-see-backlight-very-dark-gray-blue. Locking and unlocking the screen revealed the phone is in 5-dot animation, just refused to draw it.

Screen clicks, keys click, lock and unlock works, slide-lock works, but 5-dot never finishes.

Tried to use Backup Menu to restore, it didn't work. It started, then said "Chrooting ..." that usually is so fast I can't see, but it never finished chroot so hung.

Tried stock kernel to no avail.

Had to reflash and revert to an old image (3 weeks). Kind of a bummer.

Any ideas? Except "try again".
maybe creating a new backup with the enchased busybox

And restoring that backup works
i will try it (i can't live withput backupmenu!!!) i brick my device at least every 3 days
 
Posts: 48 | Thanked: 32 times | Joined on Dec 2010 @ Russia, Moscow
#46
Originally Posted by karam View Post
There seems to be a problem with
ps
i have noticed it while installing fennec6 and
airmon-ng start wlan0 (it uses ps -A)

so ps -A

showes


~ $ ps -A
ps: invalid option -- A
BusyBox v1.18.4 (Debian 1.18.4power4) multi-call binary.

Usage: ps

Show list of processes

Options:
w Wide output

~ $


that means ps is not like the old one
How to fix this ?
install procps
 

The Following 3 Users Say Thank You to Bad_Habit For This Useful Post:
Posts: 856 | Thanked: 1,681 times | Joined on Apr 2010 @ Aleppo ,Syria
#47
Thanks it fixed it
 
Posts: 268 | Thanked: 1,053 times | Joined on May 2010 @ The Netherlands
#48
Originally Posted by Bad_Habit View Post
I've noticed that several packages (and handmade patches from this forum users) depend on the old way the ps command works, not only fennec.
Originally Posted by karam View Post
There seems to be a problem with
ps
[...]
that means ps is not like the old one
How to fix this ?
The explanation for this can be found two pages back in this thread. The stock BusyBox' 'ps' accepted all parameters, whether they were valid or not. The output of `ps`, `ps ax`, and even `ps diwgsw` were all the same. This has been fixed in a later BusyBox release, and thus is fixed in busybox-power. However, this breaks some scripts that are using the invalid parameters.
I've already filed a bug for Fennec about this issue.

I'll look into reverting the correct upstream 'ps' behaviour back to the old behaviour, as some scripts are (unfortunately) relying on those invalid parameters. It seems to be a step backwards in my opinion though . If you really need to use the invalid parameters, you can install procps which does accept them as a temporary solution (thanks, Bad_Habit!).

Originally Posted by ndi View Post
Hi.

Installed BusyBox, seemed OK, but broke a few things. Not sure which broke what, but I'll recount my experience:

Installed, fiddled with it (works fine), rebooted phone.

Phone would not reboot. Entered 5-dot animation, then played the video, then screen went blank. Not locked, but black, can-see-backlight-very-dark-gray-blue. Locking and unlocking the screen revealed the phone is in 5-dot animation, just refused to draw it.

Screen clicks, keys click, lock and unlock works, slide-lock works, but 5-dot never finishes.

Tried to use Backup Menu to restore, it didn't work. It started, then said "Chrooting ..." that usually is so fast I can't see, but it never finished chroot so hung.

Tried stock kernel to no avail.

Had to reflash and revert to an old image (3 weeks). Kind of a bummer.

Any ideas? Except "try again".
Ouch, I'm very sorry this happened to you. I'm kind of puzzled since you mentioned busybox worked fine after installation. Since your device booted at least partly, /bin/busybox should've been OK after installation. My guess is that something went wrong with the symlinking part. That would also explain the fact that chroot was unavailable.

I'll contact you via PM later; I don't want to clutter this thread with debugging noise. I hope you won't have too much trouble restoring your device to its old glory.
 

The Following User Says Thank You to iDont For This Useful Post:
Posts: 48 | Thanked: 32 times | Joined on Dec 2010 @ Russia, Moscow
#49
Originally Posted by iDont View Post
you can install procps which does accept them as a temporary solution
I like the output of "top" command from procps, you could include the same into busybox
 
Posts: 284 | Thanked: 320 times | Joined on May 2010 @ Peterborough, UK
#50
I don't seem to be able to install procps - it complains about a conflict with busybox-symlinks-procps..
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 18:18.