From owner-freebsd-stable Sun Jul 8 8:33:33 2001 Delivered-To: freebsd-stable@freebsd.org Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by hub.freebsd.org (Postfix) with ESMTP id 2BE0937B405 for ; Sun, 8 Jul 2001 08:33:30 -0700 (PDT) (envelope-from olli@lurza.secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.9.3/8.9.3) id RAA71124; Sun, 8 Jul 2001 17:33:23 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Date: Sun, 8 Jul 2001 17:33:23 +0200 (CEST) Message-Id: <200107081533.RAA71124@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, "Eugene M. Kim" Reply-To: freebsd-stable@FreeBSD.ORG Subject: Re: ftpd weirdness; CWD/RETR/... handles {} specially? In-Reply-To: <20010708233841.A40891@the-7.net> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.1-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Eugene M. Kim wrote: > It depends on the case; in my situation, I'm mirroring quite a large > collection of files whose names are just wild, i.e. all sorts of special > characters embedded, some of them being shell metacharacters. Note that shell globbing is only performed on LIST. I just tried -- CWD and RETR don't expand them. If mirror has a problem mirroring such files with meta- characters, then mirror has a bug. It works fine using omi (ports/ftp/omi). Regards Oliver PS: Please DO NOT continue to ignore my Reply-To headers. Send to the list, not to myself. Thanks. -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message