From: Michael Albinus <michael.albinus@gmx.de>
To: Martin Steffen <msteffen@ifi.uio.no>
Cc: help-gnu-emacs@gnu.org
Subject: Re: tramp/ange-ftp: error in creation of dir's
Date: Mon, 19 Nov 2007 22:55:33 +0100 [thread overview]
Message-ID: <87d4u5gasq.fsf@gmx.de> (raw)
In-Reply-To: <m3d4u6ds9v.fsf@ifi.uio.no> (Martin Steffen's message of "Mon, 19 Nov 2007 19:06:20 +0100")
Martin Steffen <msteffen@ifi.uio.no> writes:
> Hi,
Hi,
> so, here is the FTP-Buffer. Note that it contains 2 parts, one that is
> ``automatically'' done when I am operating in dired mode. The very last
> part reflects the interaction, when _I_ myself use the FTP-buffer as
> interactive shell to operate the ftp-protocol.
>
> The file structure is /Volume_1 at the root. When I logon to
> the directory
>
> msteffen@192.164.1.4:
>
> I get the root / of the file system displayed in dired (as I would
> expect). Getting into the displayed directory /Volume_1
> in the dired gets me there, as exected. The next command, the
> attempted creation of "testdir", fails. So I can browse fine,
> but creating directories does not work (the same happens
> when trying to delete an empty directory).
OK. Could you, please, run a native test from the command line:
# ftp 192.164.1.4
Provide user name / password as requested. Afterwards, please apply the
following commands which we have seen in the ange-ftp buffer. This is a
test to see whether it is ange-ftp or your FTP server which behaves
unfriendly:
ftp> hash
ftp> pwd
ftp> cd /
ftp> ls -al
ftp> quote mdtm /
ftp> cd /Volume_1/
ftp> ls -al
ftp> quote mdtm /Volume_1/
ftp> mkdir /Volume_1/testdir
ftp> bye
Please show the session listing of all these commands. I suspect it is
the FTP server which runs into problems. Maybe because of this from your
test:
> ftp> pwd
> 257 "/Volume_1" is current directory.
> ftp> mkdir testdir
> 257 "/mnt/HD_a2/testdir" new directory created.
Looks like "/Volume_1" is a link or so, because "testdir" has been
created on another physical location.
> The version of the FTP server is indicated in the protocol, I
> guess. Anyway, the host is a NAS (network attached server, a D-Link
> DNS-323) and I cannot login to it, it's accessible basically via FTP (and
> samba and UPnP).
Ah. Samba on FAT32 likely. This could explain why the smb based copy
results in shortened file names.
Off topic: looks like it is possible to run native Linux on a D-Link
DNS-323. I did something similar with my Linksys NSLU2, and I'm happy
with it.
> Cheers,
>
> Martin
Best regards, Michael.
next prev parent reply other threads:[~2007-11-19 21:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3733.1195378624.18990.help-gnu-emacs@gnu.org>
2007-11-19 9:41 ` tramp/ange-ftp: error in creation of dir's Michael Albinus
[not found] ` <34247.129.240.69.93.1195465782.squirrel@webmail.uio.no>
2007-11-19 10:22 ` Michael Albinus
2007-11-19 11:07 ` Martin Steffen
[not found] ` <mailman.3785.1195470504.18990.help-gnu-emacs@gnu.org>
2007-11-19 11:30 ` Michael Albinus
2007-11-19 18:06 ` Martin Steffen
2007-11-19 21:55 ` Michael Albinus [this message]
2007-11-20 21:10 ` Martin Steffen
2007-11-20 22:46 ` Michael Albinus
2007-11-21 7:00 ` Martin Steffen
2007-11-18 9:36 Martin Steffen
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=87d4u5gasq.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=help-gnu-emacs@gnu.org \
--cc=msteffen@ifi.uio.no \
/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).