Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/sysvinit: remove inline comment from root remount
Date: Tue, 21 Oct 2014 14:25:57 -0300	[thread overview]
Message-ID: <54469725.7030600@zacarias.com.ar> (raw)
In-Reply-To: <20141021171539.GA30778@free.fr>

On 10/21/2014 02:15 PM, Yann E. MORIN wrote:

> Gustavo, All,
> 
> On 2014-10-20 16:18 -0300, Gustavo Zacarias spake thusly:
>> It breaks the root rw remount as explained in bug #7442.
>> Thanks to joymarquis at hotmail.com for pointing it out.
>>
>> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> 
> NAK, because that's what is used to decide whether to remount root RW or
> not (from system/system.mk ):
> 
>     ifeq ($(BR2_TARGET_GENERIC_REMOUNT_ROOTFS_RW),y)
>     # Find commented line, if any, and remove leading '#'s
>     define SYSTEM_REMOUNT_RW
>         $(SED) '/^#.*# REMOUNT_ROOTFS_RW$$/s~^#\+~~' $(TARGET_DIR)/etc/inittab
>     endef
>     else
>     # Find uncommented line, if any, and add a leading '#'
>     define SYSTEM_REMOUNT_RW
>         $(SED) '/^[^#].*# REMOUNT_ROOTFS_RW$$/s~^~#~' $(TARGET_DIR)/etc/inittab
>     endef
>     endif
>     TARGET_FINALIZE_HOOKS += SYSTEM_REMOUNT_RW
> 
> We must find another solution.

Searching for the comment isn't pretty, i'd just:

rwmo::sysinit:/bin/mount -o remount,rw / (sysvinit)
null::sysinit:/bin/mount -o remount,rw / (skeleton)

And nuke them when the root must be RO by searching for "mount -o
remount,rw /".

But really well done that should all move to an initscript at the S00
order that handles ALL of the filesystems at once in a predictable way
via /etc/fstab, there's no excuse.
Regards.

      reply	other threads:[~2014-10-21 17:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-20 19:18 [Buildroot] [PATCH] package/sysvinit: remove inline comment from root remount Gustavo Zacarias
2014-10-21 17:15 ` Yann E. MORIN
2014-10-21 17:25   ` Gustavo Zacarias [this message]

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=54469725.7030600@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --cc=buildroot@busybox.net \
    /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