Alexander Skwar wrote:
> So sprach Prana am Fri, Mar 09, 2001 at 12:13:18AM -0500:
>
>> See, even Pete installs Zope, nfs, heartbeat :-) And Pete doesn't want
>> to run it. Maybe he just wants to test it? So how come developer's
>> conclusion is: "If I want to install this RPM package, it means I want
>> to install it?" :-) And how can I remember 2200 RPM packages? :-)
>
>
> Well, I can understand this conclusion and think it's right - if I install a
> package, I may do so because I may know what it is and thus use it. Why
> would I install a package and not use it? I think Mdk should stay the way
> they are; ie. if a package is installed, enable it.
>
> Also the opposite is true: I would be kinda pissed if I chose to install a
> package and then it would be turned off. This makes no sense to me.
>
>> However what if we come up to a solution to add one more check box in
>> the like:
>>
>> =============================================================
>> Installation option:
>> [ ] Recommended
>> [o] Customized
>> [ ] Expert
>>
>> Option:
>> [x] Turns off network servers (daemon) by default to make Linux
>
>
> That should read: "Turn off *ALL* network servers..."
>
>> Mandrake secure and more responsive because I only want to run this
>> computer as a desktop for either workstation or development machine.
>
>
> But then, this does not make sense to me. Why install and turn off?
>
> Alexander Skwar
Some points that me irritates me about this atm.
1. Because I want to have a service installed but only run it once in a
while ?
2. I'm a newbie and press the big "install everything" button.
3. If I know I want this service running I should be able to turn it on
but it shouldn't be turned on by default,
to hinder the common "I happened to install something I don't know"
and then run a bunch of daemons
that you don't know what they do (and which exploits are found against).
4. I have a service turned off and every time I upgrade that package the
daemon is turned on again.
Joakim Bodin
