Re: postflight script failed [SOLVED]
Re: postflight script failed [SOLVED]
- Subject: Re: postflight script failed [SOLVED]
- From: Peter Bierman <email@hidden>
- Date: Fri, 4 May 2007 13:32:08 -0700
At 2:48 PM -0500 5/4/07, Fritz Anderson wrote:
Changing the cookie from #!\<tab>/usr/bin/ruby to
#!<space>/usr/bin/ruby solved the problem.
I find the Installer environment's choking on the tab, when bash did
not, to be odd, but I chalk that up to the many mysteries of
sh-vs-bash.
The #! at the beginning of a shell script is a signal to the kernel
to exec the path after the #!. You should not put any whitespace
between the #! and the path.
Many interactive shells will attempt to parse a 'shell script'
themselves before passing the file to the kernel to execute directly.
That's probably the source of the differences you see.
The installer does not treat any executable differently than any
other. It just tries to run the file, and the kernel does the rest.
-pmb
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden