It was run from the cmdline. If you do not have shell access on the server you might get your host support to assist or you can use some FTP programs to do it.
I had a somewhat similar issue with my new install of 3.0.
What I did to fix mine was to “chmod -R 777 wp-content”, then upload an image and looked at the image to determine what user apache was running as. After noting the image file was owned by “nobody” and in group “nobody” I then did a “chgrp -R nobody wp-content” followed by a “chmod -R 775 wp-content”.
After doing these steps my problem was then solved.
Hope this helps.
