From owner-freebsd-doc Tue Oct 6 12:11:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22380 for freebsd-doc-outgoing; Tue, 6 Oct 1998 12:11:54 -0700 (PDT) (envelope-from owner-freebsd-doc@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA22368 for ; Tue, 6 Oct 1998 12:11:45 -0700 (PDT) (envelope-from kelly@plutotech.com) Received: from plutotech.com (tampopo.plutotech.com [206.168.67.161]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id NAA22788; Tue, 6 Oct 1998 13:11:03 -0600 (MDT) Message-ID: <361A6B46.73B4851@plutotech.com> Date: Tue, 06 Oct 1998 13:11:02 -0600 From: Sean Kelly Organization: Pluto Technologies X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Eivind Eklund CC: Sue Blake , Greg Lehey , doc@FreeBSD.ORG Subject: Re: Dos and Don'ts References: <19981006071237.02443@follo.net> <19981006155341.C27781@freebie.lemis.com> <19981006083809.00946@follo.net> <19981006173417.64829@welearn.com.au> <19981006174328.65315@follo.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Eivind Eklund wrote: > Does the following look better? > > DON'T run pppd (as opposed to /usr/sbin/ppp) unless you either > (a) already have a working setup, or > (b) absolutely need the 2% reduction of CPU usage it will give > you. > Running the kernel PPP will not buy you much, it is harder to > setup, it is less maintained, it has fewer features, and it > will give you much more problems if you later find out you > want to put your local network online through PPP (the natd comment > below) Much better, yes! An initiate in the strange world that is FreeBSD can read the one-to-two sentences of advice and follow them without question; while the journeyman (journeyperson?) can read the reasoning why and be educated. I like to think I'm beyond the journeyman stage, but I found myself becoming suspicious of the dos and don'ts without their matching explanations. Some other observations: * Many of the dos and don'ts have a common theme that if it's already working then don't worry. How about we just factor that out into the common maxim: "If it isn't broken, don't fix it," and stick it up at the top. * "man rcsintro" ... having the machine track things is great, but sometimes the paper record kept on the shelf is more durable than a failed upgrade or other catastrophe. * "/etc/.local" ... maybe we could explicitly list all the config files that support this, to assist the newbies who wouldn't know how to determine this otherwise. Take care. --Sean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message