Firefox

Michael Curtis bazmail at bazmac.co.uk wrote: Hi, I have been having issues rolling out Firefox 3.6.x for ages. Since following the emails on this list, it seems using dmg and pkg was one on my issues. I am using the Composer diff files to make the image, but the permissions look wrong. Composer is taking my account as the owner with rwx permissions and of course when this goes over to the images machine the owner is _unknown. Who should the owner be?

This is normal, whether you're using Composer or Packagemaker/Iceberg/etc., when the original installer doesn't force a specific owner:group or if you're snapshooting a drag install.

Apple uses root:wheel for critical stuff, and root:admin for most other things in the /Applications directory. We generally deploy using root:admin on all our packages. For packaging I always log in as root. This way I get root:admin for the package. I'm hesitant to change permissions recursively within a package since you never know if a file or directory needs specific permissions that might not be obvious.

If your package has _unknown as the user or group, it could be that the target computer lacks the user account you used when making your package. Another reason to package while logged in as root.

Don

Hi,

Thanks to all those that replied. I corrected the permissions and I thought that had cracked it, but unfortunately not. Even on a clean install and installing just the application it still hangs on launch. I don't even get a full set of menus. It just says Firefox in the menu. If I force quit and relaunch it, it just appears in the dock and then quits.

I understand it is best to remove the old version first in an upgrade situation, but this is a clean install of the OS with nothing Firefox related in the build except that application.

Best wishes

Michael

Is there any reason you are using Composer diffs to create the package? Why
On Thu, Sep 9, 2010 at 2:44 PM, Michael Curtis <bazmail at bazmac.co.uk> wrote:
not just drag and drop the Firefox app into Composer to create the package? That's how I create my FF packages and I haven't had an issue yet.

Steve Wood
Director of IT
swood at integer.com

The Integer Group | 1999 Bryan St. | Ste. 1700 | Dallas, TX 75201
T 214.758.6813 | F 214.758.6901 | C 940.312.2475

I've also found that by running a pre-install script that blows away any
existing Firefox.app bundle you have fewer problems laying down the new
one.

j
-- Jared F. Nichols
Desktop Engineer, Client Services
Information Services Department
MIT Lincoln Laboratory
244 Wood Street
Lexington, Massachusetts 02420
781.981.5436

And, doing the install at either login or logout. Or, by Self Service using
On Thu, Sep 9, 2010 at 7:36 AM, Nichols, Jared - 1170 - MITLL <jared.nichols at ll.mit.edu> wrote:
a pre-install to kill running Firefox instances and deleting the app, then
installing.

Steve Wood
Director of IT
swood at integer.com

The Integer Group | 1999 Bryan St. | Ste. 1700 | Dallas, TX 75201
T 214.758.6813 | F 214.758.6901 | C 940.312.2475