From: Mathieu Othacehe <m.othacehe@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Use genimage for disk-image creation.
Date: Sun, 29 Mar 2020 20:13:30 +0200 [thread overview]
Message-ID: <877dz3t4fp.fsf@gmail.com> (raw)
In-Reply-To: <874kub9p2f.fsf@gnu.org>
Hey!
> I’m completely sold to the idea. :-)
I'm glad you like it!
> Looking at ‘image-ext2.c’ reveals that genimage actually just shells out
> to mke2fs. Indeed, I discovered that ‘mke2fs -d /my/root’ copies
> /my/root as the image’s root directory. Likewise, for ISO, it just
> shells out to ‘genisoimage’.
>
> So I think that we could avoid ‘genimage’ altogether and implement
> similar functionality for ext4/ISO in (gnu build disk-image).
Ok! One useful functionality of genimage seems to be that's its capable
of creating complex partitioning layouts. Of course we can re-implement
it in (gnu build disk-image), but I don't know how complex will it be.
Danny, I found the genimage files for each arm/aarch64 boards inside
Buildroot repository. They are a valuable source of information, but
regardless of the decision we take for (gnu build disk-image), we can
find a way to import them and store them as Guile records.
I guess I'll start a small implementation to have a clearer view of this
topic.
Thank you all for the feedback,
Mathieu
next prev parent reply other threads:[~2020-03-29 18:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 13:18 Use genimage for disk-image creation Mathieu Othacehe
2020-03-26 9:55 ` Vincent Legoll
2020-03-26 10:18 ` Efraim Flashner
2020-03-28 20:47 ` Mathieu Othacehe
2020-03-28 21:25 ` Vincent Legoll
2020-03-26 14:19 ` Ludovic Courtès
2020-03-26 15:01 ` Vincent Legoll
2020-03-29 18:13 ` Mathieu Othacehe [this message]
2020-03-26 23:24 ` Danny Milosavljevic
2020-03-29 14:44 ` Ludovic Courtès
2020-03-29 15:07 ` Danny Milosavljevic
2020-03-29 19:06 ` Vagrant Cascadian
2020-03-31 15:24 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877dz3t4fp.fsf@gmail.com \
--to=m.othacehe@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).