From owner-freebsd-hackers@FreeBSD.ORG Tue Mar 29 08:01:52 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E9776106564A for ; Tue, 29 Mar 2011 08:01:52 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id C9C898FC16 for ; Tue, 29 Mar 2011 08:01:52 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p2T81qKU043907 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 29 Mar 2011 01:01:52 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p2T81prR043906; Tue, 29 Mar 2011 01:01:51 -0700 (PDT) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA28915; Mon, 28 Mar 11 23:54:03 PST Date: Tue, 29 Mar 2011 00:53:50 -0700 From: perryh@pluto.rain.com To: matthias.andree@gmx.de Message-Id: <4d91900e.aNSfFKEtFazonwkG%perryh@pluto.rain.com> References: <8CDBB88B5271976-11D4-322B@web-mmc-d02.sysops.aol.com> <4D90EDFD.8070402@gmx.de> In-Reply-To: <4D90EDFD.8070402@gmx.de> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Keeping /etc/localtime up-to-date X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Mar 2011 08:01:53 -0000 Matthias Andree wrote: > Am 28.03.2011 19:57, schrieb dieterbsd@engineer.com: > > I have been running FreeBSD and NetBSD with /etc/localtime being > > a symlink for years and have not seen any problems as a result. > > In that case, /etc and /usr/share/timezone (or whatever) need to > be in the same physical file system ... If they're in the same physical FS there's no need for a symlink. You might as well use a hardlink.