Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 16 Sep 1998 00:16:25 -0400 (EDT)
From:      Bob K <melange@yip.org>
To:        "David E. Cross" <crossd@cs.rpi.edu>
Cc:        Terry Lambert <tlambert@primenet.com>, cracauer@cons.org, jmoss@ichips.intel.com, chet@po.cwru.edu, freebsd-current@FreeBSD.ORG
Subject:   Re: 'bug' in /bin/sh's builtin 'echo'
Message-ID:  <Pine.BSF.3.96.980916001150.9046W-100000@yip.org>
In-Reply-To: <Pine.GSO.3.95.980915213623.28206C-100000@eggbeater.cs.rpi.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980916001150.9046W-100000>