From owner-freebsd-current Mon Sep 14 20:06:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15704 for freebsd-current-outgoing; Mon, 14 Sep 1998 20:06:50 -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 UAA15691 for ; Mon, 14 Sep 1998 20:06:48 -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 XAA22690 for ; Mon, 14 Sep 1998 23:06:28 -0400 (EDT) Date: Mon, 14 Sep 1998 23:06:26 -0400 (EDT) From: "David E. Cross" To: freebsd-current@FreeBSD.ORG Subject: 'bug' in /bin/sh's builtin 'echo' 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 I have been attempting to do some network installs of SGI IRIX 6.5 machines off of a -CURRENT machine. IRIX 6.5 makes heavy use of 'echo foo\c'. By reading the manpage for echo it appears that '\c' is POSIX to not print a newline (similar to -n). In fact /bin/echo 'does the right thing' without the '-e' option. The shell builtin in /bin/sh however requires '-e' to parse \c correctly. For the moment I have inserted the '#define eflag 1' into the 'echo.c' builtin. Should this change make it into the tree 'officially'? -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message