From: Stephen Berman <stephen.berman@gmx.net>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Tramp and sftp
Date: Fri, 21 Apr 2017 15:56:49 +0200 [thread overview]
Message-ID: <87o9vpdftq.fsf@rosalinde> (raw)
In-Reply-To: <8760hy7xvg.fsf@detlef> (Michael Albinus's message of "Fri, 21 Apr 2017 14:23:31 +0200")
On Fri, 21 Apr 2017 14:23:31 +0200 Michael Albinus <michael.albinus@gmx.de> wrote:
> Stephen Berman <stephen.berman@gmx.net> writes:
>
> Hi Stephen,
>
>> For a long time I have been able to access a remote directory from Emacs
>> via the sftp protocol with Tramp. I didn't pay any attention to how
>> this worked, since it just did.
>
> In the past, the sftp protocol was implemented via tramp-sh.el. This
> didn't work reliably, so this has been moved to tramp-gvfs.el starting
> with Tramp 2.2.10. Emacs 24.5 is the first version which has bundled
> this.
It surprises me that sftp apparently works fine when invoked from bash
but not with tramp-sh. Or could there also be problems from bash?
>> But on a new system this has now
>> failed, and the reason seems to be that, although the system has dbus
>> installed, it has neither gvfs nor fuse, so the sftp invocation fails
>> with the error "Package `tramp-gvfs' not supported" (from
>> tramp-gvfs-file-name-handler). When I invoke sftp from the shell, it
>> succeeds, so that protocol itself does not depend on gvfs or fuse. I
>> tried removing sftp from tramp-gvfs-methods in the hope that this would
>> make tramp avoid using gvfs, but it didn't and access again failed. I
>> then tried rebuilding emacs --without-dbus, but this resulted in the
>> message "Host ‘xxx.xxx.xx’ looks like a remote host, ‘sftp’ can only use
>> the local host". So is there some way to access a remote directory from
>> Emacs via the sftp protocol without gvfs and fuse,
>
> No, this is not possible anymore. One fallback would be psftp, part of
> the putty package. This package does exist also for GNU/Linux systems.
>
> The other possibility is to use ssh or scp methods for connection. They
> don't need dbus and fuse.
This is a host I don't have shell access to, it only accepts ftp.
>> or must I install
>> these and configure dbus accordingly? (And if the latter, I'd be
>> grateful for any advice, since I've never done this; on the other system
>> that was evidently done by the distribution, on the new system I build
>> and configure all the packages myself.)
>
> Which system do you use? If it is a kind of GNU/Linux, the package
> manager shall install them w/o further configuration need.
Yes, that's the case with openSUSE, which I've used for years.
> If it is
> something else I don't know what to do.
I've been building a (GNU) Linux From Scratch system, which means I have
to get my hands dirty; I guess I have to get them even dirtier ;-).
Steve Berman
next prev parent reply other threads:[~2017-04-21 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 10:07 Tramp and sftp Stephen Berman
2017-04-21 12:23 ` Michael Albinus
2017-04-21 13:56 ` Stephen Berman [this message]
2017-04-21 17:16 ` Michael Albinus
2017-04-21 17:52 ` Stephen Berman
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=87o9vpdftq.fsf@rosalinde \
--to=stephen.berman@gmx.net \
--cc=help-gnu-emacs@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.
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).