From owner-freebsd-current Wed Jun 28 04:54:42 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA03565 for current-outgoing; Wed, 28 Jun 1995 04:54:42 -0700 Received: from dataplex.net (SHARK.DATAPLEX.NET [199.183.109.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA03559 for ; Wed, 28 Jun 1995 04:54:39 -0700 Received: from [199.183.109.242] by dataplex.net with SMTP (MailShare 1.0b8); Wed, 28 Jun 1995 06:54:35 -0500 X-Sender: wacky@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 28 Jun 1995 06:54:37 -0500 To: FreeBSD-current@freebsd.org (FreeBSD current) From: rkw@dataplex.net (Richard Wackerbarth) Subject: Re: Sysconfig routed setting Sender: current-owner@freebsd.org Precedence: bulk rgrimes@gndrsh.aac.dev.com writes: >Perhaps if sysinstall inforced this 4 point synopsis of what you have >to do to have your host understand routing: > > You either have to have a) a default route, b) run routed in some form > (the current defaults are good) to pick up rip packets off the wire, > c) gated (a non-trival thing to set up) or d) no network connection to > have your system work correctly. > >Give those 4 conditions the best default there is to ship the system >with (since you can't do the default route or gated configuration) is >to have routed -q started by default. > >If a person sets a default route, they can disable routed. >If a person sets up gated the can disable routed >If a person has no network connection, well, okay, it is wrong >for this one case, they could disable routed if they wanted to >free the process slot and some memory. > >IMHO, and evidently CSRG's as well, routed -q should be the default >it covers the widest cases. I support Rod's viewpoint. If we want to get fancy we can test for "gated" in the netstart code and supress the starting of "routed" there. Otherwise, what does it hurt to start it? ---- Richard Wackerbarth rkw@dataplex.net