Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Help - Buildroot-2010.11 Don't know what changed
Date: Thu, 2 Dec 2010 18:08:06 +0100	[thread overview]
Message-ID: <20101202180806.04d114c3@surf> (raw)
In-Reply-To: <AANLkTimk=w-b3jMs58sFzLG5SVEkybEsQmTVpyuS-P-O@mail.gmail.com>

On Thu, 2 Dec 2010 11:27:09 -0500
Chris Kerios <ckerios@gmail.com> wrote:

> I am working with the 2010.11 release on a PC-104 Geode LX w/Compact
> Flash card. Fedora 14.
> 
> I built a minimal system with all the defaults, no external toolchain:
> 
> Kernel = 2.6.36.1
> uClibc = .9.31.x with .9.31.x.config file
> Busybox = 1.17.x with 1.17.x.config file
> gcc = 4.3.x
> bootloader selected = grub
> 
> I have not added any files/applications to be built, so all that is
> being built is the toolchain, kernel, grub and busybox.  Everything
> downloads and builds fine!
> 
> The problem is when I copy to flash and boot the system it comes up as
> read-only!  I copy things to the flash as root and preserve all
> permissions, etc.  I've looked at the mailing list and long ago the
> threads said to have the entry in inittab remount the filesystem as RW
> and it should correct the problem.  The issue is my default inittab
> file has this entry in it so I don't understand why I am seeing this.
> 
> If I execute the command manually from the command line after logging
> in, it mounts the filesystem back as RW just fine.  Also, if I include
> a "rw" on my kernel line in grub.conf the filesystem comes in as RW.
> 
> Is this a busybox issue?  I am using all buildroot defaults.  Any
> thoughts or ideas of things I can check?

We have :

 null::sysinit:/bin/mount -o remount,rw /

in our default inittab in fs/skeleton/etc/inittab. This should
automatically remount the root filesystem as read/write when the system
boots. Maybe you are using a different filesystem skeleton ?

If not, then edit this line to be :

 ::sysinit:/bin/mount -o remount,rw /

and see if you have error messages.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2010-12-02 17:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-02 16:27 [Buildroot] Help - Buildroot-2010.11 Don't know what changed Chris Kerios
2010-12-02 16:31 ` Lionel Landwerlin
2010-12-02 16:52   ` Chris Kerios
2010-12-02 17:08 ` Thomas Petazzoni [this message]
2010-12-02 17:24   ` Chris Kerios
2010-12-02 17:31     ` Lionel Landwerlin
2010-12-03  3:41     ` Ken McGuire

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=20101202180806.04d114c3@surf \
    --to=thomas.petazzoni@free-electrons.com \
    --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