From: "Mats Löfdahl" <mats_lofdahl@yahoo.se>
To: help-gnu-emacs@gnu.org
Subject: Re: Tramp and BusyBox problem?
Date: Sun, 15 Mar 2009 22:23:29 +0100 [thread overview]
Message-ID: <gpjrkk$a0g$1@news.albasani.net> (raw)
In-Reply-To: <mailman.3258.1237145041.31690.help-gnu-emacs@gnu.org>
Michael Albinus wrote:
> Mats Löfdahl <mats_lofdahl@yahoo.se> writes:
>
>>> That's another problem. I would need Tramp traces now. Please apply
>>>
>>> (set tramp-verbose 6)
>>>
>>> and rerun your test. Afterwards, send the *debug tramp/scp root@10.0.0.3*
>>> buffer.
>> The buffer is called *tramp/scp root@10.0.0.3*, without the "debug"
>> part, at least I guess this is what you need:
>
> Sorry, typo. I meant
>
> (setq tramp-verbose 6)
>
> And I still need the *debug ...* buffer.
Right...
>> Another weird thing: The above is from connecting to root@ the
>> NAS. I've now installed bash on it and use that as my shell when I log
>> in as an ordinary user. This works but the dired buffer looks weird,
>> there are some codes surrounding the file names that I guess should
>> have been stripped at some point.
>>
>> Here's an extract:
>>
>> ----begin----
>> /scp:mats@10.0.0.3:/:
>> drwxr-xr-x 21 root root 4096 Mar 9 00:41 .
>> drwxr-xr-x 21 root root 4096 Mar 9 00:41 ..
>> -rw-r--r-- 1 root root 3 Aug 18 2004
>> .mkcert.serial
>> -rw-r--r-- 1 root root 0 Feb 23 21:55
>> .needquotacheck
>> -rw------- 1 root root 1024 Aug 18 2004 .rnd
>> -rw-r--r-- 1 root root 2 Mar 9 23:16
>> .upgrade_vol
>> drwxr-xr-x 2 root root 4096 Feb 23 21:54 bin
>> drwxr-xr-x 3 root root 12288 Feb 23 21:55 dev
>> drwxr-xr-x 10 root root 4096 Mar 13 23:51 etc
>> ----end----
>>
>> The non-ascii characters are represented as "^[" in the dired buffer
>> but may not have survived the mouse copy to thunderbird.
>
> Her I need the debug buffer as well. Maybe you can run both constellations?
It was different this time. When I connected as mats (bash), I first got
the same uname error message as for root (BusyBox). But I knew that it
_had_ worked, so I tried again and got the ugly dired buffer.
So I did the same experiment with root in a fresh instance of emacs.
This generated the uname error but did _not_ work at the second attempt.
The debug buffers from the two sessions are here:
http://www.solarphysics.kva.se/~mats/debug1.txt - root/BusyBox
http://www.solarphysics.kva.se/~mats/debug2.txt - mats/bash
next prev parent reply other threads:[~2009-03-15 21:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 23:40 Tramp and BusyBox problem? Mats Löfdahl
2009-03-03 8:12 ` Mats Löfdahl
2009-03-03 16:29 ` Michael Albinus
[not found] ` <mailman.2277.1236097624.31690.help-gnu-emacs@gnu.org>
2009-03-04 21:26 ` Mats Löfdahl
2009-03-08 11:05 ` Michael Albinus
[not found] ` <mailman.2691.1236510346.31690.help-gnu-emacs@gnu.org>
2009-03-08 16:47 ` Mats Löfdahl
2009-03-15 16:28 ` Michael Albinus
[not found] ` <mailman.3243.1237134515.31690.help-gnu-emacs@gnu.org>
2009-03-15 18:01 ` Mats Löfdahl
2009-03-15 19:23 ` Michael Albinus
[not found] ` <mailman.3258.1237145041.31690.help-gnu-emacs@gnu.org>
2009-03-15 21:23 ` Mats Löfdahl [this message]
2009-03-17 20:37 ` Michael Albinus
[not found] ` <mailman.3431.1237322291.31690.help-gnu-emacs@gnu.org>
2009-03-17 22:30 ` Mats Löfdahl
2009-03-19 16:39 ` Michael Albinus
[not found] ` <mailman.3583.1237480793.31690.help-gnu-emacs@gnu.org>
2009-03-19 20:19 ` Mats Löfdahl
2009-03-19 21:54 ` Michael Albinus
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='gpjrkk$a0g$1@news.albasani.net' \
--to=mats_lofdahl@yahoo.se \
--cc=help-gnu-emacs@gnu.org \
/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.
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).