Re: Re: Is `#!/bin/sh' configurable?
Bruce Momjian <pgman@candle.pha.pa.us>
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Alexander Klimov <ask@wisdom.weizmann.ac.il>
Cc: Doug McNaught <doug@wireboard.com>, pgsql-hackers@postgresql.org
Date: 2001-05-10T13:39:44Z
Lists: pgsql-hackers
We worked around the Ultrix /bin/sh problem for initdb. If that is the only place there is a problem, we can keep the fix for 7.2. > On 8 May 2001, Doug McNaught wrote: > > > Alexander Klimov <ask@wisdom.weizmann.ac.il> writes: > > > > > Hi. > > > > > > On some systems /bin/sh is not Burne Shell, e.g. /bin/sh is tcsh, but > > > > *violent retching sounds* > > > > IMHO, any system where /bin/sh doesn't point to an at-least-somewhat > > Bourne-compatible shell is broken by definition... Who perpetrated > > this atrocity? > > Sorry, I was misleaded by > >sh -c 'echo $SHELL' > /bin/tcsh > > The /bin/sh is sh, but not SysV compatible -- there is /bin/sh5 for that. > > Regards, > ASK > > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster > -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026