From owner-freebsd-questions  Mon Feb 10 09:55:23 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA14774
          for questions-outgoing; Mon, 10 Feb 1997 09:55:23 -0800 (PST)
Received: from cedb.dpcsys.com (CEDB.DPCSYS.com [207.124.154.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA14769
          for <questions@freebsd.org>; Mon, 10 Feb 1997 09:55:18 -0800 (PST)
Received: from localhost (dan@localhost) by cedb.dpcsys.com (8.8.2/8.8.2) with SMTP id RAA16508; Mon, 10 Feb 1997 17:39:19 GMT
Date: Mon, 10 Feb 1997 09:39:19 -0800 (PST)
From: Dan Busarow <dan@dpcsys.com>
To: Snob Art Genre <ben@narcissus.ml.org>
cc: questions@freebsd.org
Subject: Re: "no ld.so" when ftp'ing
In-Reply-To: <Pine.BSF.3.91.970210045107.16073A-100000@narcissus.ml.org>
Message-ID: <Pine.UW2.3.95.970210093644.15605E-100000@cedb>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Mon, 10 Feb 1997, Snob Art Genre wrote:
> 2) When I'm logged in as anonymous or ftp *from a remote site*, I can do 
> ls but dir gets me "no ld.so".
> 
> 3) When I'm logged in as anonymous or ftp from localhost, both ls and dir 
> get "no ld.so".

Weird.  Put your statically linked ls in the ftp user's ~/bin
directory.  That should fix your problem.

Why remote users can run ls is puzzling.

Dan
-- 
 Dan Busarow                                                  714 443 4172
 DPC Systems / Beach.Net                                    dan@dpcsys.com
 Dana Point, California  83 09 EF 59 E0 11 89 B4   8D 09 DB FD E1 DD 0C 82