From: ChenQi <Qi.Chen@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Zhangle.Yang@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V2 09/10] lighttpd: make /www diretory writable in read-only rootfs
Date: Tue, 30 Jul 2013 13:33:36 +0800 [thread overview]
Message-ID: <51F75030.4090600@windriver.com> (raw)
In-Reply-To: <CAJTo0LYSeFR29EAWWqaVVGw_YO1_u=J-UquRhaMdyNq7s6gUpQ@mail.gmail.com>
On 07/29/2013 11:56 PM, Burton, Ross wrote:
> On 29 July 2013 03:33, <Qi.Chen@windriver.com> wrote:
>> + echo "/www /var/volatile/www" > ${D}${sysconfdir}/default/readonly/lighttpd
> /www is the default lighttpd document root, where the web sites are
> stored, so putting them in a tmpfs would be very wrong indeed.
>
> Why does lightttp need write access? If it's putting logs in there
Yes. Exactly the log issue.
After some thinking, I think I'll just drop this patch.
Because even if I move the log location to /var/log/xxx, it will not
make the situation any better, as the /www directory is still not writable.
So I think, at this point, we should not do too much.
I'll assume that if the user is using a read-only rootfs and his system
is holding a website, maybe he'll just mount some writable media to /www.
Best Regards,
Chen Qi
> then they should be in /var/log, PIDs in /run and so on.
>
> Ross
>
>
next prev parent reply other threads:[~2013-07-30 5:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 2:33 [PATCH V2 00/10] Make read-only rootfs work with live images Qi.Chen
2013-07-29 2:33 ` [PATCH V2 01/10] init-live.sh: make $ROOT_MOUNT/media writable when necessary Qi.Chen
2013-07-29 2:33 ` [PATCH V2 02/10] use a uniform way to determine whether rootfs is read-only Qi.Chen
2013-07-29 2:33 ` [PATCH V2 03/10] udev: remove implicit dependency on initscripts Qi.Chen
2013-07-29 2:33 ` [PATCH V2 04/10] populate-volatile.sh: use $ROOT_DIR/var/volatile/tmp as TMPDIR Qi.Chen
2013-07-29 2:33 ` [PATCH V2 05/10] populate-volatile.sh: don't spawn background process at rootfs time Qi.Chen
2013-07-29 2:33 ` [PATCH V2 06/10] runqemu-internal: fix to start X correctly in live images Qi.Chen
2013-07-29 2:33 ` [PATCH V2 07/10] initscripts: use a uniform way to handle directories in read-only rootfs Qi.Chen
2013-07-29 2:33 ` [PATCH V2 08/10] irda-utils: make /etc/sysconfig writable " Qi.Chen
2013-07-29 15:26 ` Phil Blundell
2013-07-30 5:48 ` ChenQi
2013-07-29 2:33 ` [PATCH V2 09/10] lighttpd: make /www diretory " Qi.Chen
2013-07-29 15:56 ` Burton, Ross
2013-07-30 5:33 ` ChenQi [this message]
2013-07-29 2:33 ` [PATCH V2 10/10] openssh: make /etc/ssh directory " Qi.Chen
2013-07-29 15:59 ` Burton, Ross
2013-07-30 5:24 ` ChenQi
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=51F75030.4090600@windriver.com \
--to=qi.chen@windriver.com \
--cc=Zhangle.Yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.