This is also a very big issue for those who install "groups" of packages during the install. I know that I was recently bitten by this when I chose to install a number of "groups" of packages, and didn't realize that the masquerading and redirecting versions of inetd were installed. It took some investigation to figure out what was happening. Dave Bristel On Sat, 25 Sep 1999, Lars Wirzenius wrote: > Date: Sat, 25 Sep 1999 22:01:29 GMT > From: Lars Wirzenius <liw@iki.fi> > To: debian-devel@lists.debian.org > Subject: Running daemons without asking for permission on install > Resent-Date: 25 Sep 1999 22:03:47 -0000 > Resent-From: debian-devel@lists.debian.org > Resent-cc: recipient list not shown: ; > > "Martin Bialasinski" <martin@internet-treff.uni-koeln.de>: > > [If] I install a daemon, I want to use it. > > However, if you install a daemon by mistake, or without knowing it, > it would be nice to be alerted to this fact. Such things might happen > because you didn't know that, say, linuxconf or Gnome run daemons, or > because the program you want to install requires a daemon to be running. > I'm not sure if the correct solution to this is to ask a question on > install, but at least it's better than to do things without warning. > > Which reminds me, it might be nice for Debian to run something akin to a > port scanner locally from cron.daily or something, so that the sysadmin > will notice such problems better. (Optionally, and not reporting ports > that the sysadmin knows are OK.) > > -- > Stupid little mailer under construction, sorry for any problems. >
Attachment:
pgp7bx8evEfCn.pgp
Description: PGP signature