Openembedded Core Discussions
 help / color / mirror / Atom feed
From: ChenQi <Qi.Chen@windriver.com>
To: Chris Larson <clarson@kergoth.com>
Cc: chen_q07@163.com,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V4 09/10] irda-utils: fix for read-only rootfs
Date: Thu, 8 Aug 2013 10:10:28 +0800	[thread overview]
Message-ID: <5202FE14.70101@windriver.com> (raw)
In-Reply-To: <CABcZAN=kKF1cLeCR+SMenSBG2bRxVd==GR727XN-h72FW2ZT2w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2052 bytes --]

On 08/07/2013 10:18 PM, Chris Larson wrote:
>
> On Wed, Aug 7, 2013 at 1:08 AM, <Qi.Chen@windriver.com 
> <mailto:Qi.Chen@windriver.com>> wrote:
>
>     From: Chen Qi <Qi.Chen@windriver.com <mailto:Qi.Chen@windriver.com>>
>
>     The init script for irda writes configuration items to
>     /etc/sysconfig/irda
>     if that file is not available in system. But it's actually not
>     necessary,
>     the behavior doesn't change whether the init script writes to the
>     file or not.
>
>     Considering it issues error messages in case of a read-only
>     rootfs, I delete
>     the writing process.
>
>     [YOCTO #4103]
>     [YOCTO #4886]
>
>     Signed-off-by: Chen Qi <Qi.Chen@windriver.com
>     <mailto:Qi.Chen@windriver.com>>
>
>
> This is a start, but is incomplete, from what I can tell. As mentioned 
> in the other thread, the startup script shouldn't be using 
> /etc/sysconfig/ at all, in any form. We use /etc/default/ for our 
> startup script config files, not /etc/sysconfig/.
Yeah, I agree with you.
But when I checked the irda source code, I saw that it actually could 
ship its own init script (irda-utils-xxx/etc/irda.rc). And I think our 
init script is derived from this one. In its own init script, 
/etc/sysconfig is used.
(Of course, I still think /etc/default is a better location for its 
configuration file.)


> Also, the purpose of this block was clearly to implement a default 
> configuration, yet the recipe isn't altered to ship a default 
> configuration to provide equivalent functionality.
In its source code, there's a default configuration file, and we don't 
use that. I think there might be a reason.
So I'm not sure about this one.

If you have a patch to fix the irda issue properly, send it out and I'll 
rebase my remote branch and drop this one.

Best Regards,
Chen Qi


> -- 
> Christopher Larson
> clarson at kergoth dot com
> Founder - BitBake, OpenEmbedded, OpenZaurus
> Maintainer - Tslib
> Senior Software Engineer, Mentor Graphics


[-- Attachment #2: Type: text/html, Size: 4033 bytes --]

  reply	other threads:[~2013-08-08  2:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-07  8:08 [PATCH V4 00/10] Make read-only rootfs work with live images Qi.Chen
2013-08-07  8:08 ` [PATCH V4 01/10] init-live.sh: make $ROOT_MOUNT/media writable when necessary Qi.Chen
2013-08-07  8:08 ` [PATCH V4 02/10] use a uniform way to determine whether rootfs is read-only Qi.Chen
2013-08-07 20:29   ` Otavio Salvador
2013-08-08  2:17     ` ChenQi
2013-08-07  8:08 ` [PATCH V4 03/10] udev: remove implicit dependency on initscripts Qi.Chen
2013-08-07  8:08 ` [PATCH V4 04/10] populate-volatile.sh: use $ROOT_DIR/var/volatile/tmp as TMPDIR Qi.Chen
2013-08-07  8:08 ` [PATCH V4 05/10] populate-volatile.sh: don't spawn background process at rootfs time Qi.Chen
2013-08-07  8:08 ` [PATCH V4 06/10] runqemu-internal: fix to start X correctly in live images Qi.Chen
2013-08-07  8:08 ` [PATCH V4 07/10] initscripts: use a uniform way to handle directories in read-only rootfs Qi.Chen
2013-08-07  8:08 ` [PATCH V4 08/10] populate-volatile.sh: use 'cp -a' to avoid potential problem Qi.Chen
2013-08-08  2:50   ` ChenQi
2013-08-07  8:08 ` [PATCH V4 09/10] irda-utils: fix for read-only rootfs Qi.Chen
2013-08-07 14:18   ` Chris Larson
2013-08-08  2:10     ` ChenQi [this message]
2013-08-08  2:23       ` Khem Raj
2013-08-08  2:29         ` ChenQi
2013-08-07  8:08 ` [PATCH V4 10/10] openssh: " Qi.Chen

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=5202FE14.70101@windriver.com \
    --to=qi.chen@windriver.com \
    --cc=chen_q07@163.com \
    --cc=clarson@kergoth.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