Possible bug in bash -- basename

Article View: gnu.bash.bug

Article #762

#762

From: Don Christensen
Date: Tue, 21 Nov 1989 20:19

36 lines
1280 bytes

First, I am running bash 1.04 on a 386 clone and Interactive
UNIX sysVr3.2.

While using a script which called "basename", I noticed the following
problem:

In ksh:

prompt> echo `/bin/basename /usr/local`
local
prompt>

In bash:

prompt> echo `/bin/basename /usr/local`
.
prompt>


No matter what the argument to basename is under bash, the response is
always '.', even when it is assigned to a variable.  Has anyone else
noticed this problem?  Some may suggest work-arounds, but I need basename
to work since it is in a bunch of installed shell scripts.

The sysV basename is a shell script.  You will have to find it yourself
since it is proprietary to AT&T.

Any help will be greatly appreciated.

Thanks,
	Don
-- 
Don Christensen                | UUCP:       ...{sun}!daver!kesa!djc 
Kesa Corporation               | Internet:   djc@kesa.UUCP
Santa Clara, CA (209) 944-7068 | Home Phone: (415) 966-1842

Technical Details

Message-ID: <179@kesa.UUCP>

Path: arc1-ca.pugleaf.net!utzoo!telly!ddsw1!lll-winken!brutus.cs.uiuc.edu!usc!apple!vsi1!daver!kesa!djc

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!telly!ddsw1!lll-winken!brutus.cs.uiuc.edu!usc!apple!vsi1!daver!kesa!djc
From: djc@kesa.UUCP (Don Christensen)
Newsgroups: gnu.bash.bug
Subject: Possible bug in bash -- basename
Keywords: bash basename
Message-ID: <179@kesa.UUCP>
Date: 21 Nov 89 20:19:23 GMT
Organization: Kesa Corporation, Santa Clara
Lines: 36