Setting folder permisions

Your best bet would be to chmod 777 in the terminal.

You'd have to specify recursively:

<code>sudo chmod -R 777 /path/to/folder/of/stuff/</code>

Johannes,

You're dealling with a couple issues, here. One of them is learning to make the proper "mode" changes, of course. Another one is learning to deal with the fact that Tiger's Finder is just slightly "broken." When we use Getinfo to make changes to Ownership and/or Permissions, the changes we make are not immediately reflected. THis can be quite confusing, because it will appear as if no changes are allowed to be made. We must make any changes we want, ignoring what Getnfo shows us when making the change, then restart the Finder by pressing
b Option-Apple-Esc
and choosing "restart Finder." When theFinder relaunches, our changes will be "registered."

Using chmod in Terminal is really the best way to make changes, but you need to be very careful. For example, it is
b never
a good idea to set a mode of "777" recursively, unless you are absolutely sure that every file in the directory hierarchy should be executable. In fact, I might lean toward saying that using an "absolute mode," like "777," "666," "644," etc., is never a good idea when you are using chmod recursively. In any recursive usage, you should use symbolic mode. This is when you add or subtract a given permission using the form in this example:

chmod -R u+w /Some/File

Using symbolic modes, you could, for example, make executable files and directories (and these items only) executable for everyone like this:

chmod -R a+X /Some/Directory

Notice, in the above example, that I used a capital "X," not a lower case. This is a special feature of chmod that is available only when using symbolic modes that will set the execute bit for all users on any item that is either a directory or a file that is executable by anyone. It will
b not
set the execute bit on a file that is not otherwise executable.

Of course, an important concept to keep in mind here is that normal files (those that are not intended to by "executed") should
b never
have an execute bit set.

Scott