From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 13390@debbugs.gnu.org
Subject: bug#13390: tramp-adb hanging forever
Date: Mon, 18 Feb 2013 17:42:39 +0100 [thread overview]
Message-ID: <87sj4tk1z4.fsf@gmail.com> (raw)
In-Reply-To: <874nh9siwg.fsf@gmx.de> (Michael Albinus's message of "Mon, 18 Feb 2013 17:09:51 +0100")
Hi Michael,
Michael Albinus <michael.albinus@gmx.de> writes:
> Tramp expects, that "id -g" returns just a number. Your /system/bin/id
> behaves differently.
>
> During my tests I've found that several commands in /system/bin behave
> not exactly as expected. Thats why I have recommended to use as shell
> just "sh". In the case of SSHDroid this results in a shell which comes
> with SSHDroid, and which behaves more regular.
>
> Maybe you give it a try?
Same without specifying the path of "sh":
Tramp: Sending command `exec ssh -p 2222 -o ControlPath=/tmp/tramp.2399kbl.%r@%h:%p -o ControlMaster=auto -o ControlPersist=no -e none 192.168.0.24'
Tramp: Found remote shell prompt on `192.168.0.24'
Tramp: Opening connection for 192.168.0.24#2222 using ssh...done
byte-code: `/system/bin/id -g ' does not return a valid Lisp expression: `uid=0(root) gid=0(root) groups=0(root)
And when I run "id -g" from a shell connected to device, I have indeed
same result:
,----
| thierry@dell-14z:~/tmp/emacs-savanah-git$ ssh zte
| Welcome to DropBear SSH Server II!
| root@192.168.0.24's password:
| -sh-3.2# id -g
| uid=0(root) gid=0(root) groups=0(root)
`----
But indeed it seem there is different implementation of command "id":
,----
| thierry@dell-14z:~/tmp/emacs-savanah-git$ ssh zte
| Welcome to DropBear SSH Server II!
| root@192.168.0.24's password:
| -sh-3.2# /system/xbin/id -g
| 0
| -sh-3.2# /system/bin/id -g
| uid=0(root) gid=0(root) groups=0(root)
`----
--
Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997
next prev parent reply other threads:[~2013-02-18 16:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 18:10 bug#13390: tramp-adb hanging forever Thierry Volpiatto
2013-01-08 21:36 ` Michael Albinus
2013-01-08 21:53 ` Thierry Volpiatto
2013-01-09 7:09 ` Michael Albinus
2013-02-16 18:56 ` Michael Albinus
2013-02-16 22:21 ` Thierry Volpiatto
2013-02-18 10:42 ` Thierry Volpiatto
2013-02-18 11:05 ` Michael Albinus
2013-02-18 14:32 ` Thierry Volpiatto
2013-02-18 14:37 ` Michael Albinus
2013-02-18 14:52 ` Thierry Volpiatto
2013-02-18 16:09 ` Michael Albinus
2013-02-18 16:42 ` Thierry Volpiatto [this message]
2013-02-18 17:54 ` Michael Albinus
2013-02-18 18:18 ` Thierry Volpiatto
2013-02-18 18:26 ` Michael Albinus
2013-02-18 18:39 ` Thierry Volpiatto
2013-02-18 18:50 ` Michael Albinus
2013-02-18 19:02 ` Thierry Volpiatto
2013-02-18 19:26 ` Michael Albinus
2013-02-18 19:40 ` Thierry Volpiatto
2013-02-18 19:48 ` Michael Albinus
2013-02-18 16:14 ` Thierry Volpiatto
2013-02-18 10:53 ` Thierry Volpiatto
2013-02-18 11:02 ` Thierry Volpiatto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sj4tk1z4.fsf@gmail.com \
--to=thierry.volpiatto@gmail.com \
--cc=13390@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).