From owner-freebsd-current@FreeBSD.ORG Wed Jun 13 22:05:39 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 64C2416A46C for ; Wed, 13 Jun 2007 22:05:39 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 20CD113C4AD for ; Wed, 13 Jun 2007 22:05:38 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1Hyaxb-0007Fp-Ps for freebsd-current@freebsd.org; Thu, 14 Jun 2007 00:05:03 +0200 Received: from yehat.cs-7.com ([64.246.62.99]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 14 Jun 2007 00:05:03 +0200 Received: from c.kworr by yehat.cs-7.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 14 Jun 2007 00:05:03 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Volodymyr Kostyrko Date: Wed, 13 Jun 2007 22:43:55 +0300 Lines: 15 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: yehat.cs-7.com User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; ru-RU; rv:1.8.1.4) Gecko/20070601 SeaMonkey/1.1.2 Sender: news Subject: old bugs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2007 22:05:39 -0000 Recently bumped once again into "misc/58117: installworld /tmp/ problem". Would it be better to solve it at "once and for all" basis? This is a good choice for securing servers to make /tmp noexec. But when you did that - you'll have to face this bug again. Yes, it can be solved by specifying TMPDIR. But: - UPDATING says nothing about that; - nor documentation do; - the message is kindda cryptic and it takes time to understand whats going on. Why not document the issue or prevent it by using custom catalog? -- Sphinx of black quartz judge my vow!