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] [PATCH 1/3 v3] package/mke2img: new package
Date: Sat, 6 Dec 2014 19:20:32 +0100	[thread overview]
Message-ID: <20141206192032.7f46d261@free-electrons.com> (raw)
In-Reply-To: <7e35d73bbeb1b9e6d4cc1b1a3142fbfa4ab572d7.1417868913.git.yann.morin.1998@free.fr>

Dear Yann E. MORIN,

On Sat,  6 Dec 2014 13:29:44 +0100, Yann E. MORIN wrote:

> This new script is highly modeled from the existing genext2fs.sh, but
> was slightly refreshed, and a new, supposedly sane set of options has
> been choosen for the features we need (see above), and some new options
> were added, too, rather than relying on the arguments order or
> environment variables:
>   -b <nb-blocks>    number of blocks in the filesystem
>   -i <nb-inodes>    number of inodes in the filesystem
>   -r <pc-reserved>  percentage of reserved blocks
> * -d <root-dir>     directory containing the root of the filesystem
> * -o <img-file>     output image file
> * -G <ext-gen>      extfs generation: 2, 3, or 4
> * -R <ext-rev>      ext2 revision: 0 or 1 (1 is assumed for ext3 and ext4)
>   -l <label>        filesystem label
>   -u <uid>          filesystem UUID; if not specified, a random one is used
> 
> * Mandatory options

What about putting this in a "help" of the mke2img tool, or at least in
the comment header at the beginning of the script?

> +    # genext2fs does not generate a UUID, but fsck will whine if one is
> +    # is missing, so we need to add a UUID.

duplicate "is".

> +    # Of course, this has to happend _before_ we run fsck.

happend -> happen

> +    # Also, some ext4 metadata are based on the UUID, so we must
> +    # set it before we can convert the filesystem to ext4.
> +    # If the user did not specify a UUID, we generate a random one.
> +    # Although a random UUID may seem bad for reproducibility, there
> +    # already are so many things that are not reproducible in a

s/already are/are already/

Other than that, looks good.

Tested-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

 (on x86-64 in qemu, tested an ext4 filesystem with only the ext4
 kernel driver compiled in, and then tested an ext2 filesystem with
 only the ext2 kernel driver compiled in).

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-12-06 18:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-06 12:29 [Buildroot] [PATCH 0/3 v3] fs/ext2: misc enhancements (branch yem/fs-vol-id) Yann E. MORIN
2014-12-06 12:29 ` [Buildroot] [PATCH 1/3 v3] package/mke2img: new package Yann E. MORIN
2014-12-06 18:20   ` Thomas Petazzoni [this message]
2014-12-06 19:26     ` Yann E. MORIN
2014-12-06 12:29 ` [Buildroot] [PATCH 2/3 v3] fs/ext2: use the new mke2img host package Yann E. MORIN
2014-12-06 18:21   ` Thomas Petazzoni
2014-12-06 12:29 ` [Buildroot] [PATCH 3/3 v3] fs/ext2: add option to specify a filesystem label Yann E. MORIN
2014-12-06 14:15   ` Károly Kasza
2014-12-06 18:23   ` Thomas Petazzoni

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=20141206192032.7f46d261@free-electrons.com \
    --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