Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #179287 > unrolled thread

ftp client's "ls" is "!ls"

Back to article view | Back to linux.debian.user

Contents

  ftp client's "ls" is "!ls" Kent West <westk@acu.edu> - 2017-03-24 22:50 +0100
    Re: ftp client's "ls" is "!ls" <tomas@tuxteam.de> - 2017-03-25 08:10 +0100
      Re: ftp client's "ls" is "!ls" Kent West <westk@acu.edu> - 2017-03-25 23:10 +0100
        Re: ftp client's "ls" is "!ls" <tomas@tuxteam.de> - 2017-03-26 11:40 +0200
          Re: ftp client's "ls" is "!ls" Kent West <westk@acu.edu> - 2017-03-27 01:40 +0200
            Re: ftp client's "ls" is "!ls" Greg Wooledge <wooledg@eeg.ccf.org> - 2017-03-27 13:50 +0200
              Re: ftp client's "ls" is "!ls" Kent West <westk@acu.edu> - 2017-03-27 15:20 +0200

#179287 — ftp client's "ls" is "!ls"

[Multipart message — attachments visible in raw view] — view raw

I'm ftp'ing to a Dell/Quest K1000 System Management appliance, from a
Debian 9.0 box, and when I execute the command "ls" or "del" or do a
tab-completion, the commands act on the local directory instead of the
remote, so that "ls" acts like "!ls".

I've tried different terminals, different shells, made sure there were no
ls aliases getting in the way.

ftp from a Macintosh works fine.

How do I get my Debian's ftp ls to function properly?

Thanks!

-- 
Kent West                    <")))><
Westing Peacefully - http://kentwest.blogspot.com

[toc] | [next] | [standalone]

#179297

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, Mar 24, 2017 at 04:44:17PM -0500, Kent West wrote:
> I'm ftp'ing to a Dell/Quest K1000 System Management appliance, from a
> Debian 9.0 box, and when I execute the command "ls" or "del" or do a
> tab-completion, the commands act on the local directory instead of the
> remote, so that "ls" acts like "!ls".

This is not how it's supposed to work. At least not ls (dir and ls should
both list the remote's system directory contents).

Which ftp client are you using?

regards
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAljWFhQACgkQBcgs9XrR2kZf4gCfaZyPWIdPmlxjNgC7U8nxOLOY
H1wAnA95Lz6unQ5/ByY0E6RcIlQUWtWN
=Big8
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#179329

[Multipart message — attachments visible in raw view] — view raw

On Sat, Mar 25, 2017 at 2:02 AM, <tomas@tuxteam.de> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Fri, Mar 24, 2017 at 04:44:17PM -0500, Kent West wrote:
> > I'm ftp'ing to a Dell/Quest K1000 System Management appliance, from a
> > Debian 9.0 box, and when I execute the command "ls" or "del" or do a
> > tab-completion, the commands act on the local directory instead of the
> > remote, so that "ls" acts like "!ls".
>
> This is not how it's supposed to work. At least not ls (dir and ls should
> both list the remote's system directory contents).
>
> Which ftp client are you using?
>


westk@westkent:~$ aptitude show ftp
Package: ftp
Version: 0.17-34

I should make a correction to my description of the problem.

"ls" by itself shows the remote directory files

"ls <filename> looks to the local directory (as does "ls [tab-completion]"
or "del <filename> | [tab-completion]"). Weird stuff.

-- 
Kent

[toc] | [prev] | [next] | [standalone]

#179345

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, Mar 25, 2017 at 05:05:43PM -0500, Kent West wrote:
> On Sat, Mar 25, 2017 at 2:02 AM, <tomas@tuxteam.de> wrote:
> 
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On Fri, Mar 24, 2017 at 04:44:17PM -0500, Kent West wrote:
> > > I'm ftp'ing to a Dell/Quest K1000 System Management appliance, from a
> > > Debian 9.0 box, and when I execute the command "ls" or "del" or do a
> > > tab-completion, the commands act on the local directory instead of the
> > > remote, so that "ls" acts like "!ls".
> >
> > This is not how it's supposed to work. At least not ls (dir and ls should
> > both list the remote's system directory contents).
> >
> > Which ftp client are you using?
> >
> 
> 
> westk@westkent:~$ aptitude show ftp
> Package: ftp
> Version: 0.17-34
> 
> I should make a correction to my description of the problem.
> 
> "ls" by itself shows the remote directory files
> 
> "ls <filename> looks to the local directory

(1) I can not confirm this one (see below).

> (as does "ls [tab-completion]" or "del <filename> | [tab-completion]").
> Weird stuff.

(2) Tab completion, OTOH, picks *local* and not remote names for the
   completion list (this was somewhat expected, since it's probably
   readline-based and the authors just went an "easy" path). This is
   definitely confusing.

As to (1), I installed an ftp server (ftpd 0.17-34+b1, but that shouldn't
matter) and gave it a try. (my ftp client is ftp 0.17-31, so not very far
away from yours). Here's an extract from the session, my comments prefixed
with '#'':

  tomas@rasputin:~$ ftp localhost
  Connected to localhost.
  220 rasputin.flughafenstrasse.home FTP server (Version 6.4/OpenBSD/Linux-ftpd-0.17) ready.
  Name (localhost:tomas): 
  331 Password required for tomas.
  Password:
  230- 
  230- The programs included with the Debian GNU/Linux system are free software;
  230- the exact distribution terms for each program are described in the
  230- individual files in /usr/share/doc/*/copyright.
  230- 
  230- Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
  230- permitted by applicable law.
  230 User tomas logged in.
  # Now in my home directory (locally and remotely)
  Remote system type is UNIX.
  Using binary mode to transfer files.
  ftp> ls workbook
  # There is a file workbook in my home
  200 PORT command successful.
  150 Opening ASCII mode data connection for '/bin/ls'.
  -rw-r--r-- 1 tomas tomas 1436472 Mar 25 08:33 workbook
  # ftp can "see" it. Note the 'ls' output format -- a bit like "ls -l"
  226 Transfer complete.
  ftp> cd tmp
  250 CWD command successful.
  # changed (remotely) to ~/tmp (note: NO leading slash, relative)
  ftp> ls workbook
  200 PORT command successful.
  150 Opening ASCII mode data connection for '/bin/ls'.
  /bin/ls: cannot access workbook: No such file or directory
  # No 'workbook' in ~/tmp. This is correct.
  226 Transfer complete.
  ftp> !ls workbook
  workbook
  # ...but locally, it's still there. Note the 'simple' format,
  # as opposed to 'ls'.
  ftp>  

As already said, tab completion's behaviour is, to put it mildly,
confusing. But I'm not seeing what you see wrt. ls vs. !ls.

(now quickly purge the ftp server, before the haxxorz come :)
Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAljXi18ACgkQBcgs9XrR2kYoPACfT74hXRuQmDVBk0wSH9sJaFuw
kUgAnjWxaMuu2N2sMF9YJCE2oXOpjQS/
=aU7R
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#179415

[Multipart message — attachments visible in raw view] — view raw

On Sun, Mar 26, 2017 at 4:35 AM, <tomas@tuxteam.de> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Sat, Mar 25, 2017 at 05:05:43PM -0500, Kent West wrote:
> > On Sat, Mar 25, 2017 at 2:02 AM, <tomas@tuxteam.de> wrote:
> >
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > >
> > > On Fri, Mar 24, 2017 at 04:44:17PM -0500, Kent West wrote:
> > > > I'm ftp'ing to a Dell/Quest K1000 System Management appliance, from a
> > > > Debian 9.0 box, and when I execute the command "ls" or "del" or do a
> > > > tab-completion, the commands act on the local directory instead of
> the
> > > > remote, so that "ls" acts like "!ls".
> > >
> > > This is not how it's supposed to work. At least not ls (dir and ls
> should
> > > both list the remote's system directory contents).
> > >
> > > Which ftp client are you using?
> > >
> >
> >
> > westk@westkent:~$ aptitude show ftp
> > Package: ftp
> > Version: 0.17-34
>
>
Thanks for your responses, Tomas! They spurred me to think about the ftp
client I was using, and in doing a quick "aptitude search ftp" I found a
few other clients to try. The "ftp" client appears to be flakey, but the
tnftp client seems to work well, with tab-completion and other commands
performing as expected. (The ncftp client *almost* works, but
tab-completion doesn't see the blah.tgz.manifest file whereas it does see
the blah.tgz file, so it gives misleading info on tab-completion.)

Thanks!

-- 
Kent West                    <")))><
Westing Peacefully - http://kentwest.blogspot.com

[toc] | [prev] | [next] | [standalone]

#179437

On Sun, Mar 26, 2017 at 06:34:33PM -0500, Kent West wrote:
> The "ftp" client appears to be flakey, but the
> tnftp client seems to work well, with tab-completion and other commands
> performing as expected. (The ncftp client *almost* works, but
> tab-completion doesn't see the blah.tgz.manifest file whereas it does see
> the blah.tgz file, so it gives misleading info on tab-completion.)

lftp is also worth a look.  If you're an experienced Unix shell user,
lftp is almost ridiculously intuitive.  (That said, I haven't seriously
used FTP in many years... makes me wonder what you're actually doing
with it.)

[toc] | [prev] | [next] | [standalone]

#179452

[Multipart message — attachments visible in raw view] — view raw

On Mon, Mar 27, 2017 at 6:48 AM, Greg Wooledge <wooledg@eeg.ccf.org> wrote:

> On Sun, Mar 26, 2017 at 06:34:33PM -0500, Kent West wrote:
> > The "ftp" client appears to be flakey, but the
> > tnftp client seems to work well, with tab-completion and other commands
> > performing as expected. (The ncftp client *almost* works, but
> > tab-completion doesn't see the blah.tgz.manifest file whereas it does see
> > the blah.tgz file, so it gives misleading info on tab-completion.)
>
> lftp is also worth a look.  If you're an experienced Unix shell user,
> lftp is almost ridiculously intuitive.  (That said, I haven't seriously
> used FTP in many years... makes me wonder what you're actually doing
> with it.)
>
>
I think I tried lftp in my experiments, and it was lacking in some minor
way. Or maybe it was that tnftp just responded more quickly, or was the
last one I tried; I don't recall now.

This "Systems Management" appliance from KACE, then bought by Dell, then
bought by Quest, is marketed as the gee-whiz solution to managing hundreds
or thousands of network-attached devices (Windows PCs, Macs, Linux PCs,
tablets, etc) from an administrative standpoint. So far, after wrestling
with it for nearly a year, I'm not impressed.

For example, there is no sftp access, only ftp. (And so far, after trying
for a week, I've been unable to get it to work as how the documentation
describes. There's no way to set the ftp user (it's built-in; can't find
any configuration for it anywhere), and the only real options for ftp are
"on/off" and "writable" or not; I've set the check-box to "writable", but
so far, it ain't. Pfft. As I said, not impressed.... And the documentation?
And the support options? As I said, not impressed.)

Makes me wish I could just curl up in my nice little Debian world and leave
the non-Debian computers flailing in the wind.


-- 
Kent West                    <")))><
Westing Peacefully - http://kentwest.blogspot.com

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web