![]() |
2011-05-05
, 00:16
|
Posts: 268 |
Thanked: 1,053 times |
Joined on May 2010
@ The Netherlands
|
#42
|
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?
The Following 4 Users Say Thank You to iDont For This Useful Post: | ||
![]() |
2011-05-05
, 04:10
|
Posts: 2,225 |
Thanked: 3,822 times |
Joined on Jun 2010
@ Florida
|
#43
|
![]() |
2011-05-05
, 12:08
|
Posts: 1,680 |
Thanked: 3,685 times |
Joined on Jan 2011
|
#44
|
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?
The Following User Says Thank You to vi_ For This Useful Post: | ||
![]() |
2011-05-05
, 12:31
|
Posts: 268 |
Thanked: 1,053 times |
Joined on May 2010
@ The Netherlands
|
#45
|
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 Following User Says Thank You to iDont For This Useful Post: | ||
![]() |
2011-05-05
, 13:06
|
Posts: 539 |
Thanked: 518 times |
Joined on May 2010
@ nanaurbusiness
|
#46
|
![]() |
2011-05-05
, 13:13
|
Posts: 268 |
Thanked: 1,053 times |
Joined on May 2010
@ The Netherlands
|
#47
|
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::..
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
![]() |
2011-05-05
, 14:17
|
Posts: 328 |
Thanked: 72 times |
Joined on Oct 2010
@ Venezuela
|
#48
|
![]() |
2011-05-05
, 14:24
|
Posts: 1,680 |
Thanked: 3,685 times |
Joined on Jan 2011
|
#49
|
![]() |
2011-05-05
, 14:25
|
Posts: 268 |
Thanked: 1,053 times |
Joined on May 2010
@ The Netherlands
|
#50
|
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?