215 replies to this topic

[PaulOBrien]

64 please!

P

[paulsmith]

Quote

freeasabeer, on Jan 15 2010, 11:47, said:

Maybe... was the previous release of rsync already installed on you phone ?

I dont think so - I cannot see rsync in /system/xbin

ssh , scp both sym link to dropbear unlike most of the others that link to busybox. Not sure if thats right or wrong.

Paul

[teknologist]

Paul, on Jan 15 2010, 12:55, said:

64 please!

P

Me too...


TIA!

E

[freeasabeer]

paulsmith, on Jan 15 2010, 12:56, said:

I dont think so - I cannot see rsync in /system/xbin

ssh , scp both sym link to dropbear unlike most of the others that link to busybox. Not sure if thats right or wrong.

Paul

Hum... if you've got symlinks to dropbear, then you most probably have already installed the previous version before.
I will update rsync update package to 0.3 in a few seconds: that should correct this issue.

[freeasabeer]

teknologist, on Jan 15 2010, 13:19, said:

Me too...

TIA!

E

Paul & teknologist: for the x86_64 version I need to be back at home this evening !

[paulsmith]

Hi again,

I just tried the new 0.3 rsync - at first I thought it had worked as I didn't see any errors when applying the update.zip


The rsync file had not copied over to /system/xbin

However it must have nearly worked - It changed my dropbear sshd config from my change of port 22 to back to port 2222    (I already had the authorised keys -R part) - so it must have done some things right.

Once I copied the rsync from the zip file to /system/xbin by hand it all works.

Using ssh android shell with  rsync  from ubuntu desktop to android phone worked fine.  The other way round - in an ubuntu desktop shell using rsync to copy stuff off the android deive worked great.

Thanks for your help. Nice to have rsync

[PaulOBrien]

I'm going rsync nightly my photos from my phone to my server, then on my desktop pc do the same to pull them down. Awesome!

P

[freeasabeer]

paulsmith, on Jan 15 2010, 14:28, said:

Hi again,

I just tried the new 0.3 rsync - at first I thought it had worked as I didn't see any errors when applying the update.zip


The rsync file had not copied over to /system/xbin

However it must have nearly worked - It changed my dropbear sshd config from my change of port 22 to back to port 2222    (I already had the authorised keys -R part) - so it must have done some things right.

Once I copied the rsync from the zip file to /system/xbin by hand it all works.

Using ssh android shell with  rsync  from ubuntu desktop to android phone worked fine.  The other way round - in an ubuntu desktop shell using rsync to copy stuff off the android deive worked great.

Thanks for your help. Nice to have rsync

You know what: I never said rsync was to be found in /system/xbin... It's just because it is actually in /data/xbin
I have taken the following approach:
- if I need to modify something that is currently in /system, then let modify it in /system
- anything else that is new, just go to /data/xbin where Paul already did put its nano editor.

Edited by freeasabeer, 15 January 2010 - 02:24 PM.

[bandroid]

Hell yeah rsync!
Thank you!

[paulsmith]

"You know what: I never said rsync was to be found in /system/xbin... It's just because it is actually in /data/xbin "

Sorry my bad - I never even looked in there - just assumed it was in /system/xbin

[freeasabeer]

 

Loxley, on Jan 15 2010, 06:53, said:

Resolv.conf won't help. Busybox needs to be linked against android's own libc.

Peace

Niki

OK, I think I do have now a working busybox with resolv.conf  busybox_resolvconf_friendly.zip   569.89K   38 downloads... So the question now is: how do we get a /etc/resolv.conf that is always updated with the right values ???

Do we need a little daemon that look at net.dns1 property every minute or so and that update resolv.conf accordingly ? 

So far I have made /etc/resolv.conf a symlink to /data/local/resolv.conf and I update this latter file manually with the following script:

#!/system/bin/sh
gw=`/system/bin/getprop net.dns1`
resolvconf=/data/local/resolv.conf
echo "domain lan" >$resolvconf
echo "search lan" >>$resolvconf
echo "nameserver $gw" >>$resolvconf

Edited by freeasabeer, 17 January 2010 - 06:01 PM.

[intronauta]

stevenz, on Jan 14 2010, 22:51, said:

Made the /etc/passwd file  containing;

root::0:0:root:/data:/system/xbin/ash

Created /etc/root with

* * * * *  echo "New line" >> /data/cronout

Started crond using;

crond -l 0 -L /var/log/cron.log -c /etc (-l and -L switches are just for excessive logging)

crond tries to run scripts via /bin/sh so symlinked /bin to /system/bin to keep it happy.

And bingo, crond happily running amending a line to a file once a minute.

The crontab command needs the -c switch to change the working folder to /etc as well ifyou use that for anything.

How you symlinked /bin to /system/bin????

crond: crond (busybox 1.15.3) started, log level 0
crond: can't exec, user root cmd /bin/sh -c /data/cron/file.sh

I tried with SHELL=/system/bin/sh , but I get the same error

[Loxley]

freeasabeer, on Jan 16 2010, 15:44, said:

OK, I think I do have now a working busybox with resolv.conf... So the question now is: how do we get a /etc/resolv.conf that is always updated with the right values ???

Can anyone confirm this? I just get a "bad address" error when trying something like "wget http://google.de".

Please don't use "ping" to test, as ping is a native binary, not busybox.

It's getting interesting.

Have a nice day

Niki

[freeasabeer]

I've updated this post with my resolv.conf friendly busybox. I realize now I didn't uploaded it at the time of writing the post.
It also includes latest lscolors and crond config updates from Paul.

[Loxley]

freeasabeer, on Jan 17 2010, 19:06, said:

I've updated this post with my resolv.conf friendly busybox. I realize now I didn't uploaded it at the time of writing the post.
It also includes latest lscolors and crond config updates from Paul.

Cool. I'll give it a try tomorrow. Do you mind sharing what you did To bb?

Perhaps we should just put Googles nameservers (8.8.8.8   and 8.8.4.4) into resolv.conf.

Good night

Niki

[pulser]

Loxley, on Jan 17 2010, 18:52, said:

Cool. I'll give it a try tomorrow. Do you mind sharing what you did To bb?

Perhaps we should just put Googles nameservers (8.8.8.8   and 8.8.4.4) into resolv.conf.

Good night

Niki

Bit of a silly question, I believe, but if you put those nameservers into resolv.conf, would that make the phone use them for 'normal' browsing etc, over 3G connection? I have been wanting to do this for a while, as T-Mobile's are a bit sluggish, but not as bad recently. I found other DNS servers (like google) I can ping a lot faster than theirs.

If so, do I just need to pop in the modified busybox that reads the resolv.conf file?

If not, any ideas about how to 'setprop' them and then 'force' them to not be changed by DHCP. I can get them temporarily, but they change back if the connection drops even momentarily

Cheers

Edited by pulser, 18 January 2010 - 08:59 AM.

[freeasabeer]

No, not at all. Busybox world and android applications world are 2 separate worlds.

[Catscrash]

Wow, thats really great, thanks a lot...

I see a lot of you seem to know quite a bit about android dns-system...

please have a look at my problem here: http://android.modac...n/#entry1110270 that would be soooo great!

Thanks

[pulser]

freeasabeer, on Jan 18 2010, 09:46, said:

No, not at all. Busybox world and android applications world are 2 separate worlds.

I suspected that

I'm trying to figure out where in the Android/Linux system the actual 3G connection takes place, and if there are any scripts used to make the connection. Any ideas if there is anything in Linux that would be making the connection (I'm guessing something to do with /dev/rmnet0)

Thanks for confirming though.

[Loxley]

freeasabeer, on Jan 17 2010, 19:06, said:

I've updated this post with my resolv.conf friendly busybox. I realize now I didn't uploaded it at the time of writing the post.
It also includes latest lscolors and crond config updates from Paul.

Works like a charm over here. What did you do?

Thanks

niki