Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] base-files: Fix LSB NG Cases.
Date: Tue, 1 Sep 2015 16:26:17 -0500	[thread overview]
Message-ID: <55E617F9.3070102@windriver.com> (raw)
In-Reply-To: <1441142028.24871.19.camel@linuxfoundation.org>

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 <lixin.fnst@cn.fujitsu.com>
>> ---
>>  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
>>
> 
> 



  reply	other threads:[~2015-09-01 21:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-04  8:52 [PATCH] base-files: Fix LSB NG Cases Li xin
2015-08-25  5:03 ` Li, Xin
2015-09-01 21:13 ` Richard Purdie
2015-09-01 21:26   ` Mark Hatle [this message]
2015-09-02  2:09     ` Li, Xin
2015-09-02  2:45       ` Mark Hatle
2015-09-04  9:16         ` Li, Xin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55E617F9.3070102@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox