From owner-freebsd-ports Fri Nov 7 23:55:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA22238 for ports-outgoing; Fri, 7 Nov 1997 23:55:01 -0800 (PST) (envelope-from owner-freebsd-ports) Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA22230 for ; Fri, 7 Nov 1997 23:54:57 -0800 (PST) (envelope-from sheldonh@axl.iafrica.com) Received: from axl.iafrica.com [196.31.1.167] by lists01.iafrica.com with esmtp (Exim 1.73 #1) id 0xU5iy-0000fI-00; Sat, 8 Nov 1997 09:54:32 +0200 From: Sheldon Hearn To: Chuck Robey cc: Mark Murray , freebsd-ports@freebsd.org Subject: Re: xemacs installs world writable dir In-reply-to: Your message of "Fri, 07 Nov 1997 12:58:56 EST." Date: Sat, 08 Nov 1997 09:54:46 +0200 Message-ID: <7132.878975686@axl.iafrica.com> Sender: owner-freebsd-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 7 Nov 1997, Mark Murray wrote: > Right. I'd go with /var/tmp// (at a quick guess). Well, from my (albeit plebian) understanding of hier(7), /var/tmp is for things that need to survive reboots. I understand that /tmp is for things that can die with the box's consciousness. I don't like the idea of offering lusers a menu of abusible directories -- I'd prefer having two sticky directories to fret over per virgin box (/tmp and /var/tmp). And beautifully enough, this would mean having the package make use of something that already exists on a vanilla FreeBSD box. Gee, imagine that! ;-) On Fri, 07 Nov 1997 12:58:56 EST, Chuck Robey wrote: > Well, at a minimum, then, couldn't it respect the user's TMPDIR > variable? I would imagine that having users hiding locks in secret and mystical places would cause trouble for xemacs when it tries to work out what is and isn't locked, but I admit I don't know how it _really_ manages its locking... Sheldon.