From owner-freebsd-questions@FreeBSD.ORG Tue Dec 11 15:28:40 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D94F916A469 for ; Tue, 11 Dec 2007 15:28:40 +0000 (UTC) (envelope-from oceanare@pacific.net.sg) Received: from smtpgate2.pacific.net.sg (smtpgate2.pacific.net.sg [203.120.90.32]) by mx1.freebsd.org (Postfix) with SMTP id 386B613C448 for ; Tue, 11 Dec 2007 15:28:39 +0000 (UTC) (envelope-from oceanare@pacific.net.sg) Received: (qmail 10645 invoked from network); 11 Dec 2007 15:28:37 -0000 Received: from adsl2.dyn234.pacific.net.sg (HELO P2120.somewherefaraway.com) (oceanare@210.24.234.2) by smtpgate2.pacific.net.sg with ESMTPA; 11 Dec 2007 15:28:36 -0000 Message-ID: <475EAC9D.1020902@pacific.net.sg> Date: Tue, 11 Dec 2007 23:28:29 +0800 From: Erich Dollansky User-Agent: Thunderbird 2.0.0.6 (X11/20070826) MIME-Version: 1.0 To: Nikos Vassiliadis References: <475E0190.7030909@pacific.net.sg> <200712111718.05876.nvass@teledomenet.gr> In-Reply-To: <200712111718.05876.nvass@teledomenet.gr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: performance impact of large /etc/hosts files X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Dec 2007 15:28:40 -0000 Hi, Nikos Vassiliadis wrote: > On Tuesday 11 December 2007 05:18:40 Erich Dollansky wrote: >> >> I use hosts for filtering all unwanted content on my personal machine. > > That's not apparent. What are your filtering? all the sites I personally do not want to see. > and how do your filter using /etc/hosts? 127.0.0.1 BadHost.com > > I recall that before DNS(that's a long time ago) the mapping Yes, this was normal, a long time ago. > The only "filtering" I can imagine of, is using something like > 127.0.0.1 badhosts.com Yes. > But all you get is misinforming *your* resolver that Yes, this is what I want. Just the machine I am working on. No other machine should get any impact from this. > badhosts.com is on 127.0.0.1, that is, *you* cannot > connect to badhosts.com. Yes, this is what I want. > badhosts.com can connect to your machine just fine. Yes, if they would come through to it. > And I doubt that's what you want. This is really what I want. Just avoiding the traffic, the time and the optical disturbance caused by all those sites. I would even prefer a method as simple as hosts but linked even to my user account. Erich