From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Li xin <lixin.fnst@cn.fujitsu.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] base-files: Fix LSB NG Cases.
Date: Tue, 01 Sep 2015 22:13:48 +0100 [thread overview]
Message-ID: <1441142028.24871.19.camel@linuxfoundation.org> (raw)
In-Reply-To: <1433407956-1948-1-git-send-email-lixin.fnst@cn.fujitsu.com>
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?
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
>
next prev parent reply other threads:[~2015-09-01 21:14 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 [this message]
2015-09-01 21:26 ` Mark Hatle
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=1441142028.24871.19.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=lixin.fnst@cn.fujitsu.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