From owner-freebsd-emulation@FreeBSD.ORG Fri Sep 2 13:11:41 2005 Return-Path: X-Original-To: freebsd-emulation@FreeBSD.org Delivered-To: freebsd-emulation@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD23F16A41F for ; Fri, 2 Sep 2005 13:11:41 +0000 (GMT) (envelope-from bsam@bsam.ru) Received: from bsam.ru (gw.ipt.ru [80.253.10.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5270143D46 for ; Fri, 2 Sep 2005 13:11:41 +0000 (GMT) (envelope-from bsam@bsam.ru) Received: from bsam by bsam.ru with local (Exim 4.30; FreeBSD) id 1EBBMJ-0003LV-V3; Fri, 02 Sep 2005 17:13:31 +0400 To: freebsd-emulation@FreeBSD.org From: Boris Samorodov Date: Fri, 02 Sep 2005 17:13:31 +0400 Message-ID: <08559700@srv.sem.ipt.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: "Boris B. Samorodov" Cc: Subject: linux directory hier X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Sep 2005 13:11:41 -0000 Hello, FreeBSD-emulation list! I'm quite new to the list and far away of a linux-guru. But it so happend that I worked on acroread7 errors at pointyhat and the result was http://www.freebsd.org/cgi/query-pr.cgi?pr=85625. I need some further investigation and your help. The case with acroread7 was really in incorrect plist file at emulation/linux_base-8 port. Plist is dynamic and doesn't use @unexec command when uninstallig. Hehce we have errors at non-empty directories (ie /compat/linux/share/locale) where third party programms write files. The task is to create a static plist for emulation/linux_base-8 port. Now I should decide which directories are used only by linux_base port and which may be used by other programms. Seems to me that only root (/compat/linux) structure should be taken into consideration (without subdirectories) or some minor amount of subdirectories. I have to approaches: 1. Assume that all directories might be written (or it is far faster to implement and support). Actually it is already done at the above PR. 2. Cut directory names into two lists. If so then what is your suggestions? What road am I take? Which is preferrable for us? The first one seems better to me. Since I used at PR a recommended at Handbook redirection and redirect only stderr to /dev/null this approach looks like a good compromise. Thank you, WBR -- Boris B. Samorodov, Research Engineer InPharmtech Co, http://www.ipt.ru Telephone & Internet Service Provider