From owner-freebsd-bugs Mon Apr 28 22:00:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA25045 for bugs-outgoing; Mon, 28 Apr 1997 22:00:08 -0700 (PDT) Received: (from gnats@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA25025; Mon, 28 Apr 1997 22:00:04 -0700 (PDT) Date: Mon, 28 Apr 1997 22:00:04 -0700 (PDT) Message-Id: <199704290500.WAA25025@hub.freebsd.org> To: freebsd-bugs Cc: From: "Jin Guojun[ITG]" Subject: Re: bin/3387: sh mis-interpret the file name / awk failure Reply-To: "Jin Guojun[ITG]" Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR bin/3387; it has been noted by GNATS. From: "Jin Guojun[ITG]" To: fenner@parc.xerox.com Cc: FreeBSD-gnats-submit@freebsd.org, bugs@freebsd.org, gurney_j@resnet.uoregon.edu Subject: Re: bin/3387: sh mis-interpret the file name / awk failure Date: Mon, 28 Apr 1997 21:48:46 -0700 } That's correct. What's really going on is that "uname -v" outputs a } space at the end. } } % echo ">>`uname -v`<<" } >>FreeBSD 2.2-RELEASE #0: Mon Mar 24 11:03:31 GMT 1997 root@sundae.parc.xero } x.com:/usr/src/sys/compile/SUNDAE << } } so if you split on slashes and get the last piece, it is indeed "SUNDAE ". } awk is performing as you ask it to. Thanks for pointing it out. This tells that GNU awk is innocent. Then, the futher question is "Can we change uname to make no space at the end?" I am happy to fix it, but every one have to agree to do so. Comments? -Jin