On 9/3/07, Martin Sourada <martin.sourada@xxxxxxxxx> wrote: > Yes, most ARE, but the one with services could be useful. There is a > batch of services that are useful on most of notebooks, but are unneeded > on most of Desktops/Servers and vice versa. This does not have to be in firstboot.. this can be post-firstboot. I personally do not want to be stuck in the installer or firstboot any longer than I absolutely must. Turning services off and other customization tasks I can do after I am in the running system...in parallel with other more important activities like installing updates or reading penny-arcade. Adding a services dialog in firstboot or anaconda has the additional complication that users who are confused by it, have no mechanism to talk to other users while sitting in the installer interface or firstboot. You are giving unsuspecting users the option to turn services off before experiencing what the default system configuration. If they decide to turn things off, things they actually really need but don't understand the system well enough to know it, then you have given them the option to cripple the system before they even see what a working system is suppose to be. And you've done it in a way that makes it more difficult to get help repairing. If you want, add a well worded blurb about the existence of the services configuration tool in a firstboot page or something..but don't expose services in the installer process. Let users work with the default services, and then customize. -jef -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
