From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vincent Legoll Subject: Re: Use genimage for disk-image creation. Date: Thu, 26 Mar 2020 16:01:51 +0100 Message-ID: References: <87eetgo9o6.fsf@gmail.com> <874kub9p2f.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:48893) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jHU1F-00062r-VR for guix-devel@gnu.org; Thu, 26 Mar 2020 11:02:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jHU1E-0002aZ-R8 for guix-devel@gnu.org; Thu, 26 Mar 2020 11:02:05 -0400 In-Reply-To: <874kub9p2f.fsf@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org Sender: "Guix-devel" To: =?UTF-8?Q?Ludovic_Court=C3=A8s?= Cc: guix-devel > I=E2=80=99m completely sold to the idea. :-) Yep, LGTM too > Apparently =E2=80=98genimage=E2=80=99 supports many file systems, includi= ng ext[234] and > ISO9660, which are the two formats we support via =E2=80=98--file-system-= type=E2=80=99. > It does not support Btrfs, but =E2=80=98guix system disk-image=E2=80=99 d= oesn=E2=80=99t support > it either so far. > > Likewise, for ISO, it just shells out to =E2=80=98genisoimage=E2=80=99. You probably meant "mkisoimage" ? > So I think that we could avoid =E2=80=98genimage=E2=80=99 altogether and = implement > similar functionality for ext4/ISO in (gnu build disk-image). Do you anticipate less or similar work in reimplementing rather than reusing ? Genuinely asking, because we may want to support other image formats in the future, so reusing may have its interest too... Or is there another reason that I'm not seing, like maybe avoiding some overhead (probably not the fork/execs going through genisoimage though)... --=20 Vincent Legoll