From owner-freebsd-hackers Fri Jul 3 02:47:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA24438 for freebsd-hackers-outgoing; Fri, 3 Jul 1998 02:47:20 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA24410 for ; Fri, 3 Jul 1998 02:47:07 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id CAA06443; Fri, 3 Jul 1998 02:46:26 -0700 (PDT) Message-Id: <199807030946.CAA06443@implode.root.com> To: Garance A Drosihn cc: hackers@FreeBSD.ORG Subject: Re: Variant Link implementation, continued In-reply-to: Your message of "Fri, 03 Jul 1998 01:02:23 EDT." From: David Greenman Reply-To: dg@root.com Date: Fri, 03 Jul 1998 02:46:26 -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I agree that the possible keys (ie, variable names) for symbolic >links should not be something that's fixed at system build time. I sure don't agree with that. I also think Jordan's desire to have symlinks translated with the user environment is either not attainable or undesirable or both. I personally would rather that the info be kept in a seperate name table (like what Terry suggested). I also prefer to have a hierarchical structure (also like Terry suggested, except that I'd have the system table as a seperate autonomous thing and not attached to the init process). -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message