From owner-freebsd-questions Fri Aug 17 12:14:49 2001 Delivered-To: freebsd-questions@freebsd.org Received: from smtp1.cybersurf.net (smtp1.cybersurf.net [209.197.145.111]) by hub.freebsd.org (Postfix) with ESMTP id BFEAE37B405 for ; Fri, 17 Aug 2001 12:14:46 -0700 (PDT) (envelope-from 01031149@3web.net) Received: from 3web.net ([209.197.133.220]) by smtp1.cybersurf.net (Netscape Messaging Server 4.15) with SMTP id GI884J00.46Y for ; Fri, 17 Aug 2001 13:14:43 -0600 Received: by 3web.net (EzMTS MTSAgent 1.22b Service) ; Fri, 17 Aug 01 13:14:38 -0600 for Received: from 3web.net (10.0.0.2) by 3web.net (EzMTS MTSSmtp 1.50 Service) ; Fri, 17 Aug 01 07:52:19 -0600 for Received: by mandy.rockingd.calgary.ab.ca (sSMTP sendmail emulation); Fri, 17 Aug 2001 07:51:49 -0600 Date: Fri, 17 Aug 2001 07:51:47 -0600 From: Duke Normandin <01031149@3web.net> To: Odhiambo Washington Cc: Freebsd Questions Subject: Re: chroot'ing named(8) Message-ID: <20010817075147.A69443@mandy.rockingd.calgary.ab.ca> Mail-Followup-To: Odhiambo Washington , Freebsd Questions References: <20010817122110.A11537@rhadamanth> <20010817142800.C4803@ns2.wananchi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010817142800.C4803@ns2.wananchi.com>; from "Odhiambo Washington" on Fri, Aug 17, 2001 at 02:28:00PM X-Envelope-Receiver: Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is how your replies look in Mutt.... * setantae [20010817 14:20]: writing on the subject +'chroot'ing named(8)' setantae> setantae> I've been fighting with setting up named to run in a sandbox on +FreeBSD You will notice that in this case, "setantae>" take up an awful amount of room on the line, forcing Mutt to wrap the text. Do you know of a way that I could fix my Mutt so that your posts would be more legible? On the other hand, if you were to oblige us and use the standard '>' for quoting text, then the problem would go away. This example is mild compared to one of your subsequent replies to a thread. Thank you for considering this issue... -- -duke Calgary, Alberta, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message