[Info-vax] Wildcards using MULTINET FTP server, Linux client?

[Steven Schweda]

On Oct 24, 8:51 am, koeh... at eisner.nospam.encompasserve.org (Bob
Koehler) wrote:

> > That works fine with MULTINET - it's HP TCP/IP that gives that error.
>
>    So now you know what the solution is.  [...]

   That assumes, of course, that the problem description was
accurate, and there's precious little evidence for that.  In
fact, around here, the Debian GNU/Linux FTP client not only
sends "RMD" to the server when the user says "rm", but
"delete" doesn't do wildcards like, say, "*.*;*".  If you
want multiple files deleted, then you need to use "mdelete".
For example (talking to its own wu-ftpd server):

[...]
ftp> dir
200 PORT command successful.
150 Opening ASCII mode data connection for /bin/ls.
total 8
-rw-r--r-- 1 root root 10 Oct 24 04:02 a.b
-rw-r--r-- 1 root root 12 Oct 24 04:02 d.e.f
226 Transfer complete.
ftp> debug
Debugging on (debug=1).
ftp> rm *.*
---> RMD *.*
550 *.*: No such file or directory.
ftp> delete *.*
---> DELE *.*
550 *.*: No such file or directory.
ftp> mdelete *.*
---> PORT 10,0,0,66,135,245
---> NLST *.*
mdelete a.b? y
---> DELE a.b
250 DELE command successful.
mdelete d.e.f? y
---> DELE d.e.f
250 DELE command successful.
[...]

Note that "mdelete" works by first getting a file listing
("NLST"), and then acting on the files in that list (using
"DELE", not "RMD").

   So far, despite repeated requests, all we have are
apologies for the complete lack of useful information on
whatever the actual problem was, or its solution.  This new
copy+paste technology is a miracle, but only if it gets used.
I'm not running a MultiNet FTP server, so I don't know how it
behaves, and many things are possible, but I'd be a little
amazed if it'll do a wildcard file deletion if someone sends
it an "RMD *.*;*" command.  (And if it does, then it's not
clear that it should.)  But I'm always open to actual
evidence.  (But I'm not holding my breath.)

> [...]  Use a better product.

   In any case, there's not much evidence here that the TCPIP
FTP server does anything wrong, or even unusual or
unexpected, and no evidence at all that the MultiNet FTP
server does anything better.  Certainly not enough on which
to base a purchasing decision.

   The TCPIP FTP server has more than enough defects to keep
me annoyed, but I'm not seeing any here.