From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/6] fs/ext2: use the ext2 variant to name the generated rootfs image
Date: Thu, 14 Mar 2013 08:22:13 +0100 [thread overview]
Message-ID: <51417AA5.7050503@mind.be> (raw)
In-Reply-To: <201303122351.55358.yann.morin.1998@free.fr>
On 03/12/13 23:51, Yann E. MORIN wrote:
> So, what next? I see four options:
>
> 0- don't rename anything, continue calling it .ext2 (although it may be
> ext2, ext3 or ext4): status-quo;
> 1- only rename the fs directory, which*is* transparent
> - fs/ext2 -> fs/ext
> 2- completely rename the filesystem:
> - fs/ext2 -> fs/ext
> - BR2_TARGET_ROOTFS_EXT2 -> BR2_TARGET_ROOTFS_EXT
> but do not fix the defconfigs and boards doc. Anyway, add a deprecated
> symbol for BR2_TARGET_ROOTFS_EXT2.
> 3- same as 3, but also fix defconfigs and boards doc.
>
> For all those four options, we can add a post-fs-hook that symlinks the
> image file with the correct extension.
>
> Finally, the curent proposal (allow to specify the FS extension) is not
> incompatible with any of the above four options.
I don't have a problem with the directory and the config symbol using
ext2 - these are anyway internal kitchen. I wouldn't want to change only
the directory name and not the config symbol, because that does make
reading the code more difficult.
What is important, is that the name in the images directory has the
correct extension. This can be done either by the addition ROOTFS_TARGET
argument, or by symlinking in a post-hook. I'm slightly in favour of the
latter, because it is much simpler. On the other hand, Yann has done the
change already and it may be useful for other filesystems at some point too.
So for me, it is either Yann's implementation, or symlinking in a
post-hook.
BTW, note that the image still is an ext2 image (it can be read by ext2
code). So having the rootfs.ext4 -> rootfs.ext2 symlink is not a problem
at all.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
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
next prev parent reply other threads:[~2013-03-14 7:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 22:04 [Buildroot] [pull request v2] Pull request for branch yem-ext234 Yann E. MORIN
2013-03-07 22:04 ` [Buildroot] [PATCH 1/6] fs/ext2: enclose the ext2 options in if...endif Yann E. MORIN
2013-03-10 13:41 ` Thomas Petazzoni
2013-03-07 22:04 ` [Buildroot] [PATCH 2/6] fs/ext2: add ability to build ext3/4 too Yann E. MORIN
2013-03-10 13:52 ` Thomas Petazzoni
2013-03-11 0:20 ` Yann E. MORIN
2013-03-11 21:21 ` Thomas Petazzoni
2013-03-10 13:58 ` Thomas Petazzoni
2013-03-11 0:26 ` Yann E. MORIN
2013-03-12 17:40 ` Arnout Vandecappelle
2013-03-12 22:56 ` Yann E. MORIN
2013-03-07 22:04 ` [Buildroot] [PATCH 3/6] fs: allow image generators to specify file-extension Yann E. MORIN
2013-03-07 22:04 ` [Buildroot] [PATCH 4/6] fs/ext2: use the ext2 variant to name the generated rootfs image Yann E. MORIN
2013-03-10 13:55 ` Thomas Petazzoni
2013-03-12 17:42 ` Arnout Vandecappelle
2013-03-12 22:51 ` Yann E. MORIN
2013-03-14 7:22 ` Arnout Vandecappelle [this message]
2013-03-14 18:16 ` Yann E. MORIN
2013-03-07 22:04 ` [Buildroot] [PATCH 5/6] fs/ext2: add support for ext2 rev0 and rev1 Yann E. MORIN
2013-03-12 17:44 ` Arnout Vandecappelle
2013-03-07 22:04 ` [Buildroot] [PATCH 6/6] fs/ext2: remove count- and time-based fsck Yann E. MORIN
2013-03-12 17:46 ` Arnout Vandecappelle
2013-03-10 13:31 ` [Buildroot] [pull request v2] Pull request for branch yem-ext234 Thomas Petazzoni
2013-03-11 0:05 ` Yann E. MORIN
2013-03-17 22:20 ` Yann E. MORIN
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=51417AA5.7050503@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