ericmurphy
Registered
I've noticed that a lot of applications seem to assume that they're going to have write privileges to the /Applications directory. This is definitely an unwarranted assumption. OS X is a Unix system, which implies that it's a multi-user system. Many, if not most, of the users of a Unix system probably do not have administrative rights to the machine.
For example, I have my normal account, which does not have administrative access to the filesystem. I use this account to do normal work: Photoshop, page layout, web browsing, e-mail. I also have an administrative account, which I use for installing software and doing other administrative tasks.
It seems like most commercial software titles assume that any user is going to have administrative access to the filesystem. For example, neither Bryce 5 nor Quicken 2002 will work properly if you install them in /Applications and log in under an account that does not have write privileges to /Applications. Therefore, unless you want to leave your /Applications directory wide open, you have to install these programs in your home directory.
I've noticed that most Adobe applications (Photoshop, Illustrator, Acrobat, InDesign) try to download and install files in the /Applications directory when they're launched. Of course, they're unable to do so under a non-administrative account, and therefore generate an error messsage. Fortunately, the error is not fatal, and I can continue to use the application. But I'm beginning to wonder if I should log in as an administrator now and then and launch all my Adobe apps just so they can have all the necessary updates.
Isn't it time for Steve to knock some of these guys' heads together and tell them to learn how to properly write for OS X?
For example, I have my normal account, which does not have administrative access to the filesystem. I use this account to do normal work: Photoshop, page layout, web browsing, e-mail. I also have an administrative account, which I use for installing software and doing other administrative tasks.
It seems like most commercial software titles assume that any user is going to have administrative access to the filesystem. For example, neither Bryce 5 nor Quicken 2002 will work properly if you install them in /Applications and log in under an account that does not have write privileges to /Applications. Therefore, unless you want to leave your /Applications directory wide open, you have to install these programs in your home directory.
I've noticed that most Adobe applications (Photoshop, Illustrator, Acrobat, InDesign) try to download and install files in the /Applications directory when they're launched. Of course, they're unable to do so under a non-administrative account, and therefore generate an error messsage. Fortunately, the error is not fatal, and I can continue to use the application. But I'm beginning to wonder if I should log in as an administrator now and then and launch all my Adobe apps just so they can have all the necessary updates.
Isn't it time for Steve to knock some of these guys' heads together and tell them to learn how to properly write for OS X?
