linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Tomas Mudrunka <mudrunka@spoje.net>,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] Populate f2fs with files during mkfs.f2fs
Date: Mon, 21 Mar 2022 14:03:23 +0800	[thread overview]
Message-ID: <b491875c-c6a8-1243-35cf-649be3250b5d@kernel.org> (raw)
In-Reply-To: <f4e22b0dff793f75b5c37a170acba03c@spoje.net>

On 2022/3/19 20:55, Tomas Mudrunka wrote:
> Hello,
> i've noticed that mkfs.f2fs does not allow files to be copied to
> filesystem during formating by mkfs.f2fs.
> Do you think it would be hard to add such feature?
> 
> I understand that this might be a weird request which in some sense
> defies the definition of filesystem formating process. But there are
> also some arguments for this case.
> 
> In the world of embedded development we often need to build firmware
> images to be flashed into the device. And F2FS is one of the best suited
> filesystems for embedded and perhaps the one best for managed flash. So
> we naturaly want to use it and build into our fw images. However to
> build such image i need to create f2fs image, format it and then mount
> it using loopback, copy data to it, unmount, sync, handle errors, etc...
> And we have huge makefiles or stuff like genimage, to put all the image
> partitions and bootloaders and everything together. It just adds quite
> complexity to the embedded build systems.
> 
> Turns out that quite few filesystems already have this feature to
> simplify creating filesystem images without need for mounting or root
> permissions:
> 
> mkfs.ext4 -d ./input_directory
> mkfs.ubifs -d ./input_directory
> mkfs.jffs2 -d ./input_directory
> mkcramfs (obviously)
> mksquashfs (obviously)
> 
> would you please consider adding such feature as well?

Hi Tomas,

Can sload.f2fs satisfy this requirement?

Thanks,

> 
> Thank you
> 


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2022-03-21  6:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-19 12:55 [f2fs-dev] Populate f2fs with files during mkfs.f2fs Tomas Mudrunka
2022-03-21  6:03 ` Chao Yu [this message]
2022-03-21  7:59   ` Tomas Mudrunka
2022-03-25 16:02   ` [f2fs-dev] F2FS support in genimage Tomas Mudrunka
2022-03-28  3:25     ` Chao Yu

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=b491875c-c6a8-1243-35cf-649be3250b5d@kernel.org \
    --to=chao@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=mudrunka@spoje.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;
as well as URLs for NNTP newsgroup(s).