Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] BeagleBone: new board
Date: Wed, 11 Apr 2012 19:03:32 +0200	[thread overview]
Message-ID: <4F85B964.4020000@relinux.de> (raw)
In-Reply-To: <CA+-urNSUrDiZP60u60binQ8=HeWBuxHEjLs4DnOGGdf_akFeGg@mail.gmail.com>

Am 10.04.2012 20:18, schrieb Frank Hunleth:
> On Tue, Apr 10, 2012 at 12:56 PM, Stephan Hoffmann <sho@relinux.de> wrote:
>> at least, I prefer having ext3;-)  What would be a reason to stick to ext2?
> I had thought that Buildroot did not support creating root filesystems
> with ext3 or later. Do you run tunefs in a post-build script to add
> the journal? Also, I thought that busybox didn't support creating and
> checking ext3 or later?
I'm not sure about that. I just made the root fs as tgz and unzipped it
manually on the preformatted partition instead of dd'ing the image.
> I'm hoping that I'm wrong. I've been hearing about performance gains
> with ext4 extents and would like to see if they help on my projects.
> FWIW, I usually mount my rootfs read-only and have a writable data
> partition that can be reformatted should it get corrupted too badly.
That is, of course, a good idea. I think it's even better to run the
whole system as an initrd (if there is enough ram, of course).

This works with buildroot for the BeagleBone, too, and gives the
opportunity to have the whole system in one file.

Kind regards

Stephan
> Thanks,
> Frank


-- 
reLinux     -    Stephan Hoffmann
Am Schmidtgrund 124    50765 K?ln
Tel. +49.221.95595-19    Fax: -64
www.reLinux.de     sho at reLinux.de

  reply	other threads:[~2012-04-11 17:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-12 14:13 [Buildroot] [PATCH v2 2/2] BeagleBone: new board Frank Hunleth
2012-03-14  0:19 ` Arnout Vandecappelle
2012-03-17 20:42   ` Frank Hunleth
2012-04-07 13:13 ` Stephan Hoffmann
2012-04-09 23:27   ` Frank Hunleth
2012-04-10 16:56     ` Stephan Hoffmann
2012-04-10 18:18       ` Frank Hunleth
2012-04-11 17:03         ` Stephan Hoffmann [this message]
2012-04-12  1:06           ` Frank Hunleth

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=4F85B964.4020000@relinux.de \
    --to=sho@relinux.de \
    --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