mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] root.ext2
Date: Mon, 8 May 2017 10:02:10 +0200	[thread overview]
Message-ID: <20170508080210.7h3ie4huxkl2o4k2@pengutronix.de> (raw)
In-Reply-To: <20170507155639.GA17732@archie.localdomain>

Hi,

On Sun, May 07, 2017 at 05:56:40PM +0200, Clemens Gruber wrote:
> I noticed that the image-root-ext and image_ext2 rule still uses
> genext2fs to first create an ext2 filesystem and then uses tune2fs to
> convert it to ext3 and subsequently to ext4.
> 
> I think it is time to create ext4 images directly, otherwise we can't
> use features like flex_bg and extra_isize because they need to be
> specified at the time of creation.
> 
> To create the images, we could use make_ext4fs from the Android project
> or (probably better) the standalone fork from the LEDE project:
> https://git.lede-project.org/?p=project/make_ext4fs.git;a=summary
> 
> What do you think about this?

mkfs.ext4 in the current version can add content to the filesystem. So that
is the way to go. I started a patch for genimage to use it, but so far I'm
lacking the time to finish this.
The main problem is, that mkfs.ext4 checks /etc/mke2fs.conf by default and
looks up some stuff in /proc when deciding what to do. So it's a bit tricky
to make sure that the build host does not influence the creation of the
image.

Regards,
Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2017-05-08  8:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-07 15:56 Clemens Gruber
2017-05-08  8:02 ` Michael Olbrich [this message]
2017-05-11 16:14   ` Clemens Gruber
2017-05-12 15:50     ` Michael Olbrich

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=20170508080210.7h3ie4huxkl2o4k2@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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