Admin authorization vs Root authorization
Admin authorization vs Root authorization
- Subject: Admin authorization vs Root authorization
- From: "Perbix, Michael" <email@hidden>
- Date: Mon, 26 Jun 2006 10:22:42 -0400
- Thread-topic: Admin authorization vs Root authorization
Title: Admin authorization vs Root authorization
I have a meta-package with several components, one of which is a preference file being put into a local user account. When I use ROOT AUTH required (making the package with Iceberg) and choose the preferences folder as the default install spot, it modifies the permissions on the folder.
I know this is a bug (or perhaps design) of the installer...but how can I force authentication of a package without the path getting munged like that? Would Admin Auth be a better choice?
I am also installing a kernel extension, so that causes authentication for the whole metapackage....by not requiring authentication on the other components, they all install correctly.
What is the best manner in which to do this...I am designing custom software installs of all our used software with all customizations and preferences...I install the apps, support files, and preferences (to the template, and 2 local users).
-Mike
_______________________________________________
Michael Perbix
Lower Merion School District
Telecommunications Specialist
(610) 645-1964 - Work
(610) 896-2019 - Fax
_______________________________________________
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