I recently performed these steps on a Drupal 6 site. Everything worked as outlined in the post with the exception of a few changes to the SQL queries. `registry` and `registry_file` are called `autoload_registry` and `autoload_registry_file` in Drupal 6. Likewise, `cache_path` and `cache_bootstrap` are not in Drupal 6.
Making only the above changes allowed me to migrate away from the profile we were using to a standard install in 'sites/all' using only the command line. Afterwards the site worked great, modules were listed and enabled correctly, etc.
I've updated the snippet above to reflect the changes for Drupal 6.
I recently performed these steps on a Drupal 6 site. Everything worked as outlined in the post with the exception of a few changes to the SQL queries. `registry` and `registry_file` are called `autoload_registry` and `autoload_registry_file` in Drupal 6. Likewise, `cache_path` and `cache_bootstrap` are not in Drupal 6.
Making only the above changes allowed me to migrate away from the profile we were using to a standard install in 'sites/all' using only the command line. Afterwards the site worked great, modules were listed and enabled correctly, etc.
I've updated the snippet above to reflect the changes for Drupal 6.