From owner-freebsd-current Tue Sep 15 17:28:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17159 for freebsd-current-outgoing; Tue, 15 Sep 1998 17:28:51 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16782 for ; Tue, 15 Sep 1998 17:27:04 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from eggbeater.cs.rpi.edu (crossd@eggbeater.cs.rpi.edu [128.213.8.32]) by cs.rpi.edu (8.9.1/8.9.1) with SMTP id UAA13691; Tue, 15 Sep 1998 20:22:23 -0400 (EDT) Date: Tue, 15 Sep 1998 20:22:12 -0400 (EDT) From: "David E. Cross" To: Terry Lambert cc: 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: <199809152236.PAA09100@usr06.primenet.com> 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, Terry Lambert wrote: > Just write your shell scripts portably; that way they will work on all > platforms, back to Xenix 1.1.x, which didn't support shell functions. > That is a wonderful idea... assuming that we have access to shell script that other people write, and can go through making the needed changes. In this specific case it is next to impossible. 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*. -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message