Reply
Thread Tools
Posts: 2,225 | Thanked: 3,822 times | Joined on Jun 2010 @ Florida
#41
And, we seem to have a problem.

I haven't extensively tested this, but after the first reboot after having copied your busybox binary onto my device, right up until the reboot after I placed the original busybox back in, my device stopped resolving DNS.

Whether through ping, or through MicroB, it simply failed to reach anything when directed to it using URLs. It worked just fine when being directed at an IP address though. So www.google.com failed to go anywhere, but (local Google server's IP address) would load/ping flawlessly.

The only thing that fixed it was putting the stock busybox binary back in and rebooting...

I shall do some more extensive testing as time permits (though I'm pretty sure neither of the other two busybox binaries in this thread had this problem, as I think I remember rebooting with them), with some of the other busybox binaries available, and again with this one in case it glitched on copying, but I thought I'd let you know.

Aside from that little hitch, I haven't noticed any problems. vi_: You tested this last binary too right? Have you rebooted since then, or experienced any other problems?
 
Posts: 268 | Thanked: 1,053 times | Joined on May 2010 @ The Netherlands
#42
Originally Posted by Mentalist Traceur View Post
And, we seem to have a problem.

I haven't extensively tested this, but after the first reboot after having copied your busybox binary onto my device, right up until the reboot after I placed the original busybox back in, my device stopped resolving DNS.

Whether through ping, or through MicroB, it simply failed to reach anything when directed to it using URLs. It worked just fine when being directed at an IP address though. So www.google.com failed to go anywhere, but (local Google server's IP address) would load/ping flawlessly.

The only thing that fixed it was putting the stock busybox binary back in and rebooting...

I shall do some more extensive testing as time permits (though I'm pretty sure neither of the other two busybox binaries in this thread had this problem, as I think I remember rebooting with them), with some of the other busybox binaries available, and again with this one in case it glitched on copying, but I thought I'd let you know.

Aside from that little hitch, I haven't noticed any problems. vi_: You tested this last binary too right? Have you rebooted since then, or experienced any other problems?
This seems to be a problem with just the enhanced busybox, as I don't have this problem using the busybox deb with Nokia's configuration.

I hadn't tested the enhanced version out extensively (only some quick on-device testing if the binary was OK) before, but after installing it and rebooting, my device didn't resolve DNS either.

The cause is some enabled feature in the configuration file, as that is the only factor changed between the updated busybox binary and the updated + enhanced one. I currently don't have the time to find the exact option responsible, but if anyone has some spare time: the used configuration file for the enhanced busybox can be found on the previous page. It is probably some feature with DNS in its name. I'll look later this week into it if nobody has done it by then

On a side note, I'll make a proper announcement thread for the updated busybox package from this post tomorrow; all problems/discussion about it can be seperated from this thread then. Stay tuned!
 

The Following 4 Users Say Thank You to iDont For This Useful Post:
Posts: 2,225 | Thanked: 3,822 times | Joined on Jun 2010 @ Florida
#43
Ok, I'm both unaware of where to get the stock Nokia busybox config, nor that savvy about it's options, but the only option I found that looks like it has to do with DNS is this line in the file you have attached to the post with the binary in question:

CONFIG_DNSD=y

Looking online online it looks like this has to do with busybox's own support for domain name search. I'd check for that line first in the other busybox's configs.

- Edit -
I checked against your "drop in replacement" package sources - and indeed, in that one, config.maemo has "# CONFIG_DNSD is not set" in the same place.

I think that's the difference.

Last edited by Mentalist Traceur; 2011-05-05 at 04:24. Reason: Did some actual work
 

The Following 2 Users Say Thank You to Mentalist Traceur For This Useful Post:
Posts: 1,680 | Thanked: 3,685 times | Joined on Jan 2011
#44
Originally Posted by Mentalist Traceur View Post
And, we seem to have a problem.

I haven't extensively tested this, but after the first reboot after having copied your busybox binary onto my device, right up until the reboot after I placed the original busybox back in, my device stopped resolving DNS.

Whether through ping, or through MicroB, it simply failed to reach anything when directed to it using URLs. It worked just fine when being directed at an IP address though. So www.google.com failed to go anywhere, but (local Google server's IP address) would load/ping flawlessly.

The only thing that fixed it was putting the stock busybox binary back in and rebooting...

I shall do some more extensive testing as time permits (though I'm pretty sure neither of the other two busybox binaries in this thread had this problem, as I think I remember rebooting with them), with some of the other busybox binaries available, and again with this one in case it glitched on copying, but I thought I'd let you know.

Aside from that little hitch, I haven't noticed any problems. vi_: You tested this last binary too right? Have you rebooted since then, or experienced any other problems?
How odd, I don't appear to have any issues with this new version. Ping works fine, DNS resolution works fine. I wonder if it is related to your installation of 'real' ping?

Also I went to great lengths to carefully add the symlinks required for all the new busybox commands. I was careful to NOT overwrite anything that was already in use (i.e. overwrite some 'real' programs with symlinked busyboxed versions).

Everything seems to be fine.
__________________
N900: One of God's own prototypes. A high-powered mutant of some kind never even considered for mass production. Too weird to live, and too rare to die.
 

The Following User Says Thank You to vi_ For This Useful Post:
Posts: 268 | Thanked: 1,053 times | Joined on May 2010 @ The Netherlands
#45
Originally Posted by vi_ View Post
How odd, I don't appear to have any issues with this new version. Ping works fine, DNS resolution works fine. I wonder if it is related to your installation of 'real' ping?

Also I went to great lengths to carefully add the symlinks required for all the new busybox commands. I was careful to NOT overwrite anything that was already in use (i.e. overwrite some 'real' programs with symlinked busyboxed versions).

Everything seems to be fine.
The issue only appeared after a reboot. It has been fixed now. A new .config has been attached to the post with the enhanced BusyBox. The enhanced binary on the server has also been updated (and verified to be working ).

I almost got the content of the soon-to-be-posted announcement thread ready. I'll wait for this thread to disappear from the "Active Topics" list from TMO to avoid potential confusion

Edit: vi_: I almost forgot to ask: how did you create the new symlinks mentioned in your post? By editing debian/busybox.links and recompiling, manually, scripted, or ..? If not manually, would you mind sharing your script/busybox.links/.. file with me? That would save me lots of time packaging up the enhanced BusyBox, or creating an installer of some sort for it
Could you reply via PM (to avoid cluttering of this thread)?

Last edited by iDont; 2011-05-05 at 12:47.
 

The Following User Says Thank You to iDont For This Useful Post:
Posts: 539 | Thanked: 518 times | Joined on May 2010 @ nanaurbusiness
#46
Just wanted to drop a thanks and ask if its correct that I get a busybox upgrade even if I pinned everything like adviced on page 3.

edit: nevermind, I reapplied the pin script for busybox only and now it's working.

Greetz,

..::J4ZZ::..

Last edited by J4ZZ; 2011-05-05 at 13:12.
 
Posts: 268 | Thanked: 1,053 times | Joined on May 2010 @ The Netherlands
#47
Originally Posted by J4ZZ View Post
Just wanted to drop a thanks and ask if its correct that I get a busybox upgrade even if I pinned everything like adviced on page 3.

Greetz,

..::J4ZZ::..
What application said there was an BusyBox upgrade?

HAM shouldn't say there is an update even if you haven't pinned the package and apt-upgrade should say something along the lines of:
Code:
Nokia-N900:~# apt-get upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages have been kept back:
  busybox busybox-symlinks-busybox busybox-symlinks-console-tools busybox-symlinks-dnsutils busybox-symlinks-ifupdown busybox-symlinks-iputils-ping
  busybox-symlinks-net-tools busybox-symlinks-procps busybox-symlinks-psmisc busybox-symlinks-realpath busybox-symlinks-time libsdl-mixer1.2
 
Posts: 328 | Thanked: 72 times | Joined on Oct 2010 @ Venezuela
#48
Ok so what's final word? how do upgrade to the new version?
 
Posts: 1,680 | Thanked: 3,685 times | Joined on Jan 2011
#49
Originally Posted by carlon View Post
Ok so what's final word? how do upgrade to the new version?
Just wait this one out for a very short while, iDont is still finishing the packages.

If you are REALLY desperate to install this you need to install the packages he has compiled a couple of pages back, then download the enhanced busybox binary and put that in your /bin, then carefully create new symlinks for each of the busybox commands. Everything you need to know is in this thread. Otherwise hang tight for a day or so and it will hit the repos.

Be careful messing about with busybox! If you bugger up your local copy (on the phone) you WILL need to restore from a backup of the rootfs, failling that a rootfs reflash. You have been warned!
__________________
N900: One of God's own prototypes. A high-powered mutant of some kind never even considered for mass production. Too weird to live, and too rare to die.
 

The Following 2 Users Say Thank You to vi_ For This Useful Post:
Posts: 268 | Thanked: 1,053 times | Joined on May 2010 @ The Netherlands
#50
Originally Posted by carlon View Post
Ok so what's final word? how do upgrade to the new version?
The last two pages were about the enhanced binary. I guess you're talking about the updated-but-not-enhanced one? If so, just download the debian packages from this post and install those as you would install any other .deb file.

I was really just about to post the proper announcement thread; you'll see it in a minute. Any discussion about the packages can be further discussed there.

Edit: vi_: unfortunately, it can't be in the repo's without running into dependency problems AFAIK. Nokia made a metapackage explicitly depend on a specific BusyBox version. This is fixed in the CSSU (which replaces the metapackage), but not everyone has got the CSSU installed :-/
(Creative) workarounds to get it in the repo's without breaking anything are appreciated of course!


Edit 2: Please continue discussion about the packages in the following thread: http://talk.maemo.org/showthread.php?p=1000644

Last edited by iDont; 2011-05-05 at 14:43.
 

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


 
Forum Jump


All times are GMT. The time now is 02:12.