From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.windriver.com (mail.windriver.com [147.11.1.11]) by mail.openembedded.org (Postfix) with ESMTP id 7A5B477008 for ; Tue, 1 Sep 2015 21:26:18 +0000 (UTC) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail.windriver.com (8.15.2/8.15.1) with ESMTPS id t81LQIuu014537 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL) for ; Tue, 1 Sep 2015 14:26:18 -0700 (PDT) Received: from msp-dhcp31.wrs.com (172.25.34.31) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.3.235.1; Tue, 1 Sep 2015 14:26:18 -0700 To: References: <1433407956-1948-1-git-send-email-lixin.fnst@cn.fujitsu.com> <1441142028.24871.19.camel@linuxfoundation.org> From: Mark Hatle Organization: Wind River Systems Message-ID: <55E617F9.3070102@windriver.com> Date: Tue, 1 Sep 2015 16:26:17 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <1441142028.24871.19.camel@linuxfoundation.org> Subject: Re: [PATCH] base-files: Fix LSB NG Cases. X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Sep 2015 21:26:20 -0000 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit On 9/1/15 4:13 PM, Richard Purdie wrote: > On Thu, 2015-06-04 at 16:52 +0800, Li xin wrote: >> -/tset/LSB.fhs/var/tmp/tmp-tc. >> >> The LSB Core test requires the /var/tmp directory supports creation of files. >> And the mount tmpfs on /var/volatile cause the /var/tmp directory can't be >> writable for non-root users. > > This change doesn't look correct to me, its a pretty fundamental change > to the way the system operates and certainly needs more thought and > justification than the few lines above. > > Surely if its a non-root users issue, the problem is permissions, not > the tmpfs anyway? I agree.. How is /var/volatile mounted in your environment? /var/volatile should be mounted as a tmpfs with default root only permissions. (basefiles: fstab) A directory, /var/volatile/tmp should be constructed (after volatile is mounted) with perms 01777. (initscripts: populate-volatile.sh) /var/tmp should be a symbolic link to /var/volatile/tmp. (meta/files/fs-perms.txt) All of this will result in a /var/tmp that permits any user to write to it (as it should), but keep it in the volatile area. You should figure out what part of this is not working properly. (If I had to guess it's the mount of the volatile and create of the tmp dir is not working for you -- or you have a system where the default mount rules / init scripts have been modified in some way.) > Cheers, > > Richard > >> Signed-off-by: Li Xin >> --- >> meta/recipes-core/base-files/base-files/fstab | 1 - >> 1 file changed, 1 deletion(-) >> >> diff --git a/meta/recipes-core/base-files/base-files/fstab b/meta/recipes-core/base-files/base-files/fstab >> index d79a016..458ec70 100644 >> --- a/meta/recipes-core/base-files/base-files/fstab >> +++ b/meta/recipes-core/base-files/base-files/fstab >> @@ -4,7 +4,6 @@ >> proc /proc proc defaults 0 0 >> devpts /dev/pts devpts mode=0620,gid=5 0 0 >> tmpfs /run tmpfs mode=0755,nodev,nosuid,strictatime 0 0 >> -tmpfs /var/volatile tmpfs defaults 0 0 >> >> # uncomment this if your device has a SD/MMC/Transflash slot >> #/dev/mmcblk0p1 /media/card auto defaults,sync,noauto 0 0 >> -- >> 1.8.4.2 >> > >