From owner-freebsd-current Tue Sep 15 21:31:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27189 for freebsd-current-outgoing; Tue, 15 Sep 1998 21:31:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from yip.org ([142.154.6.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27184 for ; Tue, 15 Sep 1998 21:31:51 -0700 (PDT) (envelope-from melange@yip.org) Received: from localhost (melange@localhost) by yip.org (8.8.8/8.8.8) with SMTP id AAA25290; Wed, 16 Sep 1998 00:16:26 -0400 (EDT) (envelope-from melange@yip.org) Date: Wed, 16 Sep 1998 00:16:25 -0400 (EDT) From: Bob K To: "David E. Cross" cc: Terry Lambert , cracauer@cons.org, jmoss@ichips.intel.com, chet@po.cwru.edu, freebsd-current@FreeBSD.ORG Subject: Re: 'bug' in /bin/sh's builtin 'echo' In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 15 Sep 1998, David E. Cross wrote: > On Wed, 16 Sep 1998, Terry Lambert wrote: [snip] > > > What is one supposed to do when integrating a FreeBSD system into a > > > netwrok where the hosts will call 'rsh -l foo bar echo baz\c' and need > > > that to print out without the newline This is not a hypothetical, this is > > > what IRIX *does*. > > > > Set up an environment for the user "foo" that include a ~/bin in the path, > > and defines a ~/bin/echo that "does the right thing", i.e.: > > > > #!/bin/sh > > /bin/echo -e $* > > I already tried that. echo is a shell builtin, and is given precedence > over binaries in the files system, I found no way to turn that > 'feature'off. Hmm. I could be completely off, but what if one set up an alias that would map echo to ~/bin/echo? Might that work? melange@yip.org - "Slightly tacky but completely entertaining" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message