From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 8 16:50:55 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0C0016A49E for ; Wed, 8 Nov 2006 16:50:55 +0000 (UTC) (envelope-from lamont@scriptkiddie.org) Received: from sploit.scriptkiddie.org (sploit.scriptkiddie.org [216.231.47.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4276E43D7D for ; Wed, 8 Nov 2006 16:50:33 +0000 (GMT) (envelope-from lamont@scriptkiddie.org) Received: from sploit (sploit [216.231.47.214]) by sploit.scriptkiddie.org (8.12.11/8.12.11) with ESMTP id kA8GoVGs013503 for ; Wed, 8 Nov 2006 08:50:31 -0800 (PST) Date: Wed, 8 Nov 2006 08:50:31 -0800 (PST) From: Lamont Granquist To: freebsd-hackers@freebsd.org In-Reply-To: <200611060950.kA69ogbY072242@lurza.secnetix.de> Message-ID: References: <200611060950.kA69ogbY072242@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: Yet another magic symlinks implementation 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: Wed, 08 Nov 2006 16:50:56 -0000 AFS also has an @sys variable which is useful for network filesystem mounted binaries and software for multiple architectures through a single globally unique path: http://www.openafs.org/pages/doc/AdminReference/auarf234.htm#HDRSYS And I'd vote with Oliver on preferring variant symlinks for flexibility: On Mon, 6 Nov 2006, Oliver Fromme wrote: > I'm afraid that I don't like NetBSD's "magic symlinks" very > much. It's less flexible than variant symlinks because it > only supports a fixed set of variables. As far as I can > tell, it does not solve any of the tasks described above. > > Therefore I would really like to see your port of DragonFly > BSD's variant symlinks comitted to FreeBSD. Of course, it > could be a compile-time option in case there are people who > don't want the code in their kernel at all. But you have > to set a sysctl anyway to enable it globally (it's disabled > by default on DragonFly).