From: Artem Bityutskiy <dedekind@infradead.org>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: linux-mtd@lists.infradead.org, vapier.adi@gmail.com
Subject: Re: [PATCH 3/3] mkfs.ubifs: use libubi to format UBI volume
Date: Wed, 13 May 2009 11:46:54 +0300 [thread overview]
Message-ID: <1242204414.27996.175.camel@localhost.localdomain> (raw)
In-Reply-To: <71cd59b00905130138t7fc974ffub5efb8c78198388e@mail.gmail.com>
On Wed, 2009-05-13 at 10:38 +0200, Corentin Chary wrote:
> > On Sat, 2009-05-09 at 11:41 +0200, Corentin Chary wrote:
> >> libubi is now used to format directly UBI volume.
> >> Typing mkfs.ubifs /dev/ubi0_0 is now possible.
> >> dtypes should be ok as they are taken from UBIFS code.
> >
> > Did you test that this works fine on UBI volume and there
> > are no regressions when you output to a file?
>
> I did some test with and without --root, it worked fine.
> But I'll do some more test with the corrected patch.
Ok, thanks.
> Because I wanted mkfs.ubifs to work without this parameter, like other mkfs.*.
> I know mounting an empty volume will works, but we should also be able
> to use mkfs.ubifs to format
> empty volumes.
Ok.
> >> ino->uid = cpu_to_le32(st->st_uid);
> >> ino->gid = cpu_to_le32(st->st_gid);
> >> - ino->uid = cpu_to_le32(st->st_uid);
> >> - ino->gid = cpu_to_le32(st->st_gid);
> >> ino->mode = cpu_to_le32(st->st_mode);
> >> ino->flags = cpu_to_le32(use_flags);
> >> ino->data_len = cpu_to_le32(data_len);
> >
> > Why the 2 lines are removed?
>
> Theses should have been removed in another patch, but look, they are
> here twice =).
Ah, OK.
> > Yeah, I think you should either ask the user, or just refuse
> > writing to it. Users may just 'ubiupdatevol -t' to erase the
> > volume before invocating mkfs.ubifs.
> >
> > Probably it is easier for now to just remove whole
> > 'erase_volume()' ?
> >
> mkfs.ext{2/3/4} and mkfs.vfat don't ask for confirmation
> I believe mkfs.reiserfs does.
> But I won't hurt to ask.
> Maybe first we can remove erase_volume(), and then, in another patch,
> add erase volume with confirmation.
Well, OK, let's be consistent with other mkfs'es then.
> New patch is comming at the end of the week ...
Thanks!
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2009-05-13 8:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-09 9:41 [PATCH 0/3] libubi / mkfs.ubifs #2 Corentin Chary
2009-05-09 9:41 ` [PATCH 1/3] libubi: add ubi_is_mapped() function Corentin Chary
2009-05-09 9:41 ` [PATCH 2/3] libubi: fix multiple memory corruptions Corentin Chary
2009-05-09 9:41 ` [PATCH 3/3] mkfs.ubifs: use libubi to format UBI volume Corentin Chary
2009-05-13 8:12 ` Artem Bityutskiy
2009-05-13 8:38 ` Corentin Chary
2009-05-13 8:46 ` Artem Bityutskiy [this message]
2009-05-11 7:02 ` [PATCH 0/3] libubi / mkfs.ubifs #2 Corentin Chary
2009-05-11 7:19 ` Artem Bityutskiy
2009-05-11 7:21 ` Artem Bityutskiy
2009-05-11 7:23 ` Artem Bityutskiy
2009-05-11 7:37 ` Mike Frysinger
2009-05-11 7:58 ` Corentin Chary
2009-05-11 14:29 ` Artem Bityutskiy
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=1242204414.27996.175.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=corentin.chary@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=vapier.adi@gmail.com \
/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