Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] axfs: add new filesystem type
Date: Tue, 13 Oct 2015 23:14:19 +0200	[thread overview]
Message-ID: <561D742B.4050800@mind.be> (raw)
In-Reply-To: <20151013202408.GA4161@free.fr>



On 13-10-15 22:24, Yann E. MORIN wrote:
> Ariel, All,
> 
> On 2015-10-13 09:12 -0300, Ariel D'Alessandro spake thusly:
>> El 05/10/15 a las 15:53, Arnout Vandecappelle escribi?:
> [--SNIP--]
>>>> +define ROOTFS_AXFS_CMD
>>>> +	$(HOST_DIR)/usr/bin/mkfs.axfs -s -a $(TARGET_DIR) $@
>>>
>>>  I'm not sure if we really want to give the -s option. Is it very verbose?
>>> Generally I like a bit of feedback about how the filesystem is built, and we do
>>> get it for e.g. squashfs.
>>
>> Yeah, I think it's very verbose. But on the other hand, with the -s
>> option it's too quiet.
>> I don't know what is the main criteria. Maybe you can tell me, here's
>> the output of two mkfs.axfs executions with and without -s option:
>>
>> --
>> $ ./mkfs.axfs -s -a target/ output/
>> number of files:                   585
>> number of 4KB nodes:               1752
>>
>> Total image size:                       5111906
>> --
>>
>> --
>> $ ./mkfs.axfs -a target/ output/
> [--SNIP--]
>> Total image size:                       5111906
> 
> IMHO, the non-silent version is way too verbose. I'd prefer that the -s
> flag be used.
> 
> Arnout, OK for you?

 I believe mksquashfs is equally verbose. But it's OK for me either way.

 Regards,
 Arnout

-- 
Arnout Vandecappelle      arnout dot vandecappelle at essensium dot com
Senior Embedded Software Architect . . . . . . +32-478-010353 (mobile)
Essensium, Mind division . . . . . . . . . . . . . . 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:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2015-10-13 21:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-05 16:55 [Buildroot] [PATCH v2 0/2] Add support for AXFS filesystem type Ariel D'Alessandro
2015-10-05 16:55 ` [Buildroot] [PATCH v2 1/2] axfsutils: add new package Ariel D'Alessandro
2015-10-05 18:39   ` Arnout Vandecappelle
2015-10-13 12:06     ` Ariel D'Alessandro
2015-10-05 16:55 ` [Buildroot] [PATCH v2 2/2] axfs: add new filesystem type Ariel D'Alessandro
2015-10-05 18:53   ` Arnout Vandecappelle
2015-10-05 18:59     ` Ezequiel Garcia
2015-10-05 19:09       ` Arnout Vandecappelle
2015-10-13 12:12     ` Ariel D'Alessandro
2015-10-13 20:24       ` Yann E. MORIN
2015-10-13 21:14         ` Arnout Vandecappelle [this message]
2015-10-13 20:53     ` Yann E. MORIN
2015-10-14 15:50       ` Ariel D'Alessandro
2015-10-13 21:14 ` [Buildroot] [PATCH v2 0/2] Add support for AXFS " Thomas Petazzoni
2015-10-14 16:05   ` Ariel D'Alessandro
2015-10-14 17:06     ` 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=561D742B.4050800@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