From owner-freebsd-arch Mon Jun 26 12:26:58 2000 Delivered-To: freebsd-arch@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id EBDBD37BAE3; Mon, 26 Jun 2000 12:26:55 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id MAA97090; Mon, 26 Jun 2000 12:26:55 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Mon, 26 Jun 2000 12:26:55 -0700 (PDT) From: Kris Kennaway To: Nate Williams Cc: Will Andrews , arch@FreeBSD.ORG Subject: Re: Disabling inetd? In-Reply-To: <200006261615.KAA18734@nomad.yogotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 26 Jun 2000, Nate Williams wrote: > I think it's a bad idea, and assumes that the 'default' installation is > a box that's running 24/7 connected directly to the internet. That certainly is the assumption - I think it's a quite valid one in this day and age. If such a thing were to be done, I'd expect a sysinstall knob to turn inetd back on, so you'd just have to tick an extra box during sysinstall - hardly a big price to pay. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message