From: Efraim Flashner <efraim@flashner.co.il>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: dannym@scratchpost.org, 45020@debbugs.gnu.org
Subject: [bug#45020] [PATCH 0/2] image: Add system field.
Date: Wed, 9 Dec 2020 12:27:41 +0200 [thread overview]
Message-ID: <X9CmncYV5Kcegakt@E5400> (raw)
In-Reply-To: <87tusvz3nf.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
On Wed, Dec 09, 2020 at 11:15:32AM +0100, Mathieu Othacehe wrote:
>
> Hello Efraim,
>
> > I'm not sure about i686-linux being an efi-raw type. I always assumed
> > they were all not EFI.
>
> The "efi-raw" image type is actually an hybrid image type supporting EFI
> and BIOS legacy boot methods.
>
> Maybe we should then rename "raw" to "bios-efi-raw" or
> "bios-efi-hybrid-raw", what do you think?
My hope is to eventually produce an image for mips64el again, which
would need an ext2 formatted /boot partition. I'm hoping to make it not
too hard to hack that in in the future :)
Perhaps it makes sense to name them according to the architecture more?
we have arm32-raw and aarch64-raw, how about i686-raw and x86_64-raw?
Make it clear exactly what architecures they target. Then we can
continue with the hybrid bios/efi images anyway.
> Thanks,
>
> Mathieu
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-12-09 10:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 10:53 [bug#45020] [PATCH 0/2] image: Add system field Mathieu Othacehe
2020-12-03 10:53 ` [bug#45021] [PATCH 1/2] " Mathieu Othacehe
2020-12-03 20:41 ` Danny Milosavljevic
2020-12-04 8:12 ` Mathieu Othacehe
2020-12-04 9:01 ` Danny Milosavljevic
2020-12-05 10:24 ` Mathieu Othacehe
2020-12-03 10:53 ` [bug#45022] [PATCH 2/2] image: Rename "raw" image-type to "efi-raw" Mathieu Othacehe
2020-12-03 13:11 ` [bug#45020] [PATCH 0/2] image: Add system field zimoun
2020-12-09 8:25 ` Efraim Flashner
2020-12-09 10:15 ` Mathieu Othacehe
2020-12-09 10:27 ` Efraim Flashner [this message]
2020-12-11 16:50 ` Ludovic Courtès
2020-12-12 8:30 ` Mathieu Othacehe
2020-12-12 12:34 ` zimoun
2020-12-13 14:15 ` Ludovic Courtès
2020-12-15 14:11 ` zimoun
2020-12-15 21:56 ` Ludovic Courtès
2020-12-12 17:51 ` Ludovic Courtès
2020-12-15 9:58 ` Mathieu Othacehe
2021-07-16 2:04 ` Maxim Cournoyer
2021-08-30 16:24 ` Mathieu Othacehe
2021-10-05 8:26 ` Mathieu Othacehe
2021-10-11 12:06 ` bug#45020: " Mathieu Othacehe
2020-12-13 14:59 ` [bug#45020] " Danny Milosavljevic
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=X9CmncYV5Kcegakt@E5400 \
--to=efraim@flashner.co.il \
--cc=45020@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=othacehe@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).