Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!ncar!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!pitt!darth!investor.pgh.pa.us!rbp
From: rbp@investor.pgh.pa.us (Bob Peirce #305)
Newsgroups: comp.sys.next
Subject: Re: /bin/[ (was Upgrade2.0.app -- Woes)
Keywords: Upgrade2.0
Message-ID: <1991Mar14.122436.954@investor.pgh.pa.us>
Date: 14 Mar 91 12:24:36 GMT
References: <8701@plains.NoDak.edu> <353@rosie.NeXT.COM>
Reply-To: rbp@investor.pgh.pa.us (Bob Peirce #305)
Organization: Cookson, Peirce & Co., Pittsburgh, PA
Lines: 13

In article <353@rosie.NeXT.COM> news@NeXT.COM (news) writes:
>This bug in Upgrade2.0 surfaces when /bin/test on the system you are upgrading  
>has been altered or touched.  To support the Bourne shell, /bin/[ is a link to  
>/bin/test: when Upgrade2.0 sees that /bin/[ has been modified, it tries to  
>bring up an attention panel to ask you if the file should be preserved or  
>overwritten.  Unfortunately, it becomes confused by the metacharacter in the  
>file's name and an error ensues.

Why is this?  I thought [ was built into sh.  I don't have this link on
my SysV machine.  Is this a BSDism?
-- 
Bob Peirce, Pittsburgh, PA				  412-471-5320
...!uunet!pitt!investor!rbp			rbp@investor.pgh.pa.us