multisite Installer/Upgrader questions

I didn't take a bite into Multisite installations until 2.2-rc1 - I do have a question or two about the Installer/Upgrader in regards to how and when it detects "permissions" issues of the target directory (eg. /path/to/username/htdocs/gallery2/)

In all of the fresh multisite installations I created, the Installer would always detect a target directory that is writeable and it would put a notice (with a "recheck" or "continue" option) for you to take action upon. And everytime I encounter that notice (a good reminder for the careless admin), I would execute a small shell script to issue the following commands:

chown -R username:group /path/to/usr/home/username/htdocs/gallery2/
chmod 755 /path/to/usr/home/username/htdocs/gallery2/

the Installer would continue on and complete the multisite setup.

However, when I was converting standalone 2.1.2 sites to 2.2.1 multisites, that same "notice" would only appear at random. Before I open the Installer to begin the conversion process, here's what I do:

mv /path/to/usr/home/username/htdocs/gallery2/config.php /path/to/usr/home/username/.
mv /path/to/usr/home/username/htdocs/gallery2/.htaccess /path/to/usr/home/username/.
rm -R /path/to/usr/home/username/htdocs/gallery2/*
chmod 777 /path/to/usr/home/username/htdocs/gallery2/

the Installer runs as expected, then finally it would tell me to open the URL address of the new multisite (converted from a standalone) to run the upgrader instead (since it's not a fresh install) - i guess this is the default behavior since all it did was create the skeleton files and multisite config.php file (reusing the same ~/g2data/ and database info)
so I'm wondering if there's anything I'm doing wrong that's hindering the Upgrader to detect /path/to/usr/home/username/htdocs/gallery2/ as still being writeable - like it does with fresh multisite installations.

please advise, thanks!

hrm, the multisite Installer requires a writeable target directory right or (manually create writeable skeleton files for it to write to (config.php, etc...)? cus the Installer notice (during a fresh multisite install) always advises me to "chmod 755 /path/to/usr/home/username/htdocs/gallery2/" (not ~/g2data) - but only appears at random during standalone -> multisite conversions.

the ~/g2data/ directory which resides on /path/to/usr/home/username/g2data/ already has a www:www / 777 permissions set so I never have to touch it

please advise, thanks.

ok, so far, here's what I understand so please correct me if I'm mistaken:

the G2 Installer/Upgrader regardless if it's a standalone or multisite will always:

- after core is installed/upgraded, detect permissions set for the "target directory" -> if set to 777, output a notice to issue a "chmod 755 /path/to/gallery2/" -> [recheck] (if the admin took the action or [continue] buttons

- after core is installed/upgraded, detect whether "config.php" is writeable -> if set 666/777, output a notice to issue a "chmod 644 /path/to/gallery2/config.php" -> [recheck] (if the admin took the action or [continue] buttons

(i have yet to see this in my encounters) - detect permissions set for the "g2data directory"? -> output a notice/error

thank you!