Re: How to execute script as root, and then an another script on behalf of an ordinary user
Re: How to execute script as root, and then an another script on behalf of an ordinary user
- Subject: Re: How to execute script as root, and then an another script on behalf of an ordinary user
- From: Karl Kuehn <email@hidden>
- Date: Wed, 5 Jan 2011 22:29:54 -0800
On Jan 5, 2011, at 10:05 AM, eveningnick eveningnick wrote:
>> This indicates that you are trying to use Apple's PackageMaker. While it is the Apple tool for this, there are better ones available for free. I would suggest using Iceberg or Packages (for "old style" and "flat file" packages respectively).
>
> Thanks, i'll take a look at that.
> I just wanted to make it Apple-look-like so that installation process does not differ from any other installations users had made before, even though there's a lot of addtional work is done underneath.
I think you are missing an important thing here. .pkg files are documents, not applications. PackageMaker is a program that creates these files, and Iceberg/Packages is another. The user experience is identical, and the installer program (Installer.app) does not differentiate .pkgs from one source or the other.
[snip]
>> Yes, there are lots. As a simple example: why are you assuming that there is only one person logged in, or that there is even one person logged in to the computer. Both cases are valid.
>
> I guess i will have to ps -x | grep loginwindow and execute "launchctl bsexec" for every instance of loginwindow? if there's no users logged
> in, the loop will never be executed. Otherwise, it'll execute for every user who's logged in (well, just like in that example on that link).
>
>> We don't know exactly what you are trying to do, backing out a step or two might be a really good idea. There are a lot of people on this list that can probably better help you out if you give them the information they need to help you.
>
> It's an NKE Kext , which is autoloaded by a "starter"-daemon and whose status is displayed by an agent in a status bar. After installing, i want these daemon and agent to be launched immediately, without reboot.
I understand the convince and elegance that you are going for, but it might not be worth it. I am a bit prejudiced in this area as I worked on InstaDMG for a long time, but you should be aware that there are cases where the volume that your package is being installed to is not the root volume, so loading Kexts automatically should only be done with great care (a similar argument for the toolbar).
And there are just so many variables in this area that I am not sure that it is really worth doing. While it is brutal, and we should aim for better, I am with Greg on this one and I think that a reboot is the best option.
--
Karl Kuehn
email@hidden
_______________________________________________
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