On Thu, Apr 02 2009, Celejar wrote:
> On Thu, 02 Apr 2009 10:12:54 -0500
> Manoj Srivastava <sriva...@ieee.org> wrote:
>
> ...
>
>> There are mechanisms by which the site admin can tailor the
>> selection of daemons that start -- but the default should be I
>> installed it, and I installed it for a reason, so I want the thing
>> running.
>
> But perhaps I don't want it to run until after I modify the default
> configuration. I may install a web server, but I may want it to serve
> only over a LAN interface, and not over my public interface. I know I
> can block this at the firewall, but I want defense in depth, and I'm
> suggesting that there can be perfectly common use cases where I want
> the thing installed, and eventually even running, but not just yet, or
> right now.
Then, knowing the system default, you take action not to let the
server start. Or you modify the config file asap (often before the
system finishes the upgrade.
See, there are two equally viable options here. Use debconf to
configure the daemon, so most people can install, answer questions, and
be on their merry way --- or not start and let the user configure it as
they will.
Some like it one way, some the other. What the maintainr has to
judge is which set of users to please, since you can't please
everyone.
--
The universe is all a spin-off of the Big Bang.
Manoj Srivastava <sriva...@acm.org> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
