[Frugalware-devel] enabling services by default in upstart?
Christian Hamar [krix]
krics at linuxforum.hu
Wed Jun 20 17:07:42 CEST 2007
2007. 06. 15, péntek keltezéssel 21.31-kor VMiklos ezt írta:
> hi,
>
> in sysvinit, you have a default: if you install rc.foo then it'll be
> never started by default, we have to write an install scriptlet to
> enable a service
>
> in upstart, you can choose the default:
>
> 1) enable each job by default, so that we have to write a scriptlet to
> disable it
>
> 2) disable jobs by default, just like in sysvinit
Well. I dont know upstart but, all services enabled at scriptlet or
disabled right now no ? I mean like in sysvinit, you install a package
putting upstart script into place and then it will be enabled by
default ?
I think its bad. Why enable default a cups server or anything else, if i
dont have a printer. Or why enable acpid or anything else that installed
by default or by mass-install :S
I like the normal way like how its now.
BTW whats matter if we write disable (or enable) to a package install
scriptlet ?
We cant calculate how our users thinking and what is good for them. (If
enabled by default or disabled) Who will deal that we enable this or
not ?
And afterall if we force users to disable or enable stuffs, then all the
same. Does not matter if we say disable to all or enable to all. We
force users to enable OR disable services
My suggestion is that enable services by default which is NEED for
system up and running good (like how is now).
Regards
-krix-
More information about the Frugalware-devel
mailing list