So sprach Joakim Bodin am Fri, Mar 09, 2001 at 11:26:53PM +0100:
> 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 ?
Uhm, then turn it off, but...
> 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).
Hmm, thinking about it - hmm, as Mandrake is targeted at the newbie kind of
user, I begin to think that even after an install, a service should default
to being turned off. Yes, it's beginning to make sense. If someone knows
that he wants something, than it's easier for him to turn the service
intentionally on.
But then again, someone may not know what he wants. Suppose a new linux
user, who just read, that linux comes with an email server. He knows that
he wants an email server, but fails to see that postfix is an email server.
Now the service is turned off - he comes to the conclusion, that "Linux is
not working" because he expected to have an email server when installing
Linux. What about these kind of users?
> 4. I have a service turned off and every time I upgrade that package the
> daemon is turned on again.
Yes, this should not happen. Upgrading packages should not change the
whether a service is turned on or off.
Alexander Skwar
--
How to quote: http://learn.to/quote (german) http://quote.6x.to (english)
Homepage: http://www.digitalprojects.com | http://www.iso-top.de
iso-top.de - Die guenstige Art an Linux Distributionen zu kommen
Uptime: 5 days 8 hours 53 minutes
