On Mon, 2007-09-03 at 15:18 +0200, Martin Sourada 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. And we'd like to get rid of > as much unneeded services as possible, so if we target the default ones > with a thought of the target platform, it would be IMHO more effective. > Maybe it could go to anaconda, but personally I think that first boot is > better place for that. Actually, the bigger problem is the concept that everything has to be a "system service run from an initscript". To pick a specific case -- the fact that bluetooth daemons get started by an initscript as a service is really not what you want at this point. You instead want them being started based on the existence of the hardware probably as a hal callout[1]. The same can really be said for most of the things which start by default currently which are maybe not needed in some cases. Services are for _servers_. And having to enable them (via system-config-services or chkconfig or ...) to use them makes sense because that's hardly going to be the only configuration you need to do for them. Jeremy [1] Bluetooth specifically is tracked with https://bugzilla.redhat.com/show_bug.cgi?id=222315 and the more general tracker bug is https://bugzilla.redhat.com/show_bug.cgi?id=222312 -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
