unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <othacehe@gnu.org>
To: Gabriel Wicki <gabriel@erlikon.ch>
Cc: 66448@debbugs.gnu.org
Subject: [bug#66448] [PATCH] image: Add 'lba partition label.
Date: Fri, 13 Oct 2023 15:02:25 +0200	[thread overview]
Message-ID: <87h6mud6am.fsf@gnu.org> (raw)
In-Reply-To: <kpa6kvayhetwqfffoqrdplz5kbvhlmmrp72p3cs5m6donlcvyt@tkbqehy5evfc> (Gabriel Wicki's message of "Wed, 11 Oct 2023 10:55:23 +0200")


Hello,

> I didn't follow the whole source tree to figure out how all of this
> works, but this tiny change makes the image partition show up as LBA.

I had a closer look, this flag has no effect at all. If the 'esp flag is
set then the MBR partition type is set to 0xEF (EFI partition). If the
flag is removed, then depending on the file-system type: "fat16"
or "fat32", the partition type will be 0x0E or 0x0C which are
respectively FAT16 with LBA an FAT32 with LBA.

I guess that by removing the 'esp flag and adding the 'lba flag you
ended up with an LBA partition. That was the consequence of removing the
'esp flag, not adding the 'lba flag.

The partition type is specified in the partition->dos-type procedure of
(gnu system image). The corresponding types can be found here:
https://en.wikipedia.org/wiki/Partition_type.

We could improve the documentation here by stating that fat16 and fat32
partitions are by default LBA compatible, but the source modification in
not needed.

Thanks,

Mathieu




  reply	other threads:[~2023-10-13 13:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10 16:29 [bug#66448] [PATCH] image: Add 'lba partition label Gabriel Wicki
2023-10-11  8:51 ` Mathieu Othacehe
2023-10-11  8:55   ` Gabriel Wicki
2023-10-13 13:02     ` Mathieu Othacehe [this message]
2023-10-17 12:27       ` Gabriel Wicki
2023-10-17 13:12         ` bug#66448: " Mathieu Othacehe

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=87h6mud6am.fsf@gnu.org \
    --to=othacehe@gnu.org \
    --cc=66448@debbugs.gnu.org \
    --cc=gabriel@erlikon.ch \
    /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).