Okay, I can't resist adding my two cents even though it looks like the OP is long gone.
I agree with most of the rationale already said. My experience with graphical installers such as Mandriva and Ubuntu have been that they oversimplify the partitioning process to the point of being dangerous. In order to avoid scaring the newbie with too much information, they don't provide enough detail into what they are actually about to do to your drive.
Something else I'll add is that a distro's installer reflects the character of the distro. If you're marketing your distro to the "shoot first, aim later" types, then by all means give them an autopilot installer. The entire Slackware experience is built on providing documentation with the assumption that the user will bother to read it before he jumps in and starts breaking things. Slack's installer (and update process, and package management, and startup scripts, and networking, and ...) is extremely well documented and shouldn't be at all daunting if you've done some preparation. If a user isn't willing or able to do that prior to performing the non-trivial task of installing an OS, then Slackware isn't going to be a good fit for them anyway.
|