Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Ext4 rootfs option
Date: Wed, 8 Feb 2012 23:10:48 +0100	[thread overview]
Message-ID: <201202082310.49254.arnout@mind.be> (raw)
In-Reply-To: <20120208222445.0dc487d7@skate>

On Wednesday 08 February 2012 22:24:45 Thomas Petazzoni wrote:
> Hello,
> 
> Le Wed, 08 Feb 2012 17:14:00 +1000,
> Mark Constable <markc@renta.net> a ?crit :
> 
> > Is it worth my while to provide some (first time newbie) patches
> > for a ext4 rootfs?
> 
> Sure!
> 
> How do you generate ext4 images? You use genext2fs and then some other
> commands to enable ext4-specific features? Is there another utility?

 I currently use genext2fs, followed by  tune2fs to add the journal and 
e2fsck to fix the incorrect FS version  number.  But it's extremely 
inefficient, especially since genext2fs first builds the filesystem in 
memory before committing to the output image.  Not good when you want to
create a 500GB partition :-)

 Regards,
 Arnout

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2012-02-08 22:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08  7:14 [Buildroot] Ext4 rootfs option Mark Constable
2012-02-08 21:24 ` Thomas Petazzoni
2012-02-08 22:10   ` Arnout Vandecappelle [this message]
2012-02-08 22:15     ` Peter Korsgaard
2012-02-09 14:02       ` Michael S. Zick
2012-02-09 22:36       ` Arnout Vandecappelle

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=201202082310.49254.arnout@mind.be \
    --to=arnout@mind.be \
    --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