site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com If your package requires authorization, then the script is running as root. -pmb Thanks for the info. Thanks, On Jun 1, 2005, at 1:12 PM, Pavol Markovic wrote: Try cd $2/foldername open . PM On Jun 1, 2005, at 6:56 PM, Derrick Griffel wrote: Thanks, Derrick _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/pavol.markovic%40centru... This email sent to pavol.markovic@centrum.sk Derrick Griffel Intriguing Development Inc. 816-229-6768 ext. 12 www.idevelop.net _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/bierman%40apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... It might be possible to use 'open' to launch an app as root into a regular user session, but not to use 'open' as root to get the finder to open a window. You can probably use 'osascript' to send an AppleEvent to the finder asking it to open the window you want. You could also look for the real (vs effective) uid that your script is running as, and use 'su' to switch to that user to run the 'open' command. At 1:28 PM -0500 6/1/05, Derrick Griffel wrote: I just tried that but unfortunately with the same results. The folder does not open. I know it is changing to the correct directory though, because if I substitute "open MyApp.app" for "open .", the application gets launched from the installer. But for whatever strange reason, I cannot just get the folder to open. It also seems add that it will open the application fine, but not open the folder. I haven't tried it in Installer, but I was able to do this in situations where open folder didn't work. I am trying to open a specific folder after installation. I have a postflight script that contains the following line: open $2/foldername. I would expect this to open the directory named foldername located at the install location returned by the $2 variable. Unfortunately, the directory does not open. However, if I change this to: open -a $2/foldername/application.app, The postflight script WILL launch my application located inside the folder. Does anyone have any ideas on why I can get the script to launch an application after install, but not open a folder? This email sent to bierman@apple.com This email sent to site_archiver@lists.apple.com