From: "Thomas Schmitt" <scdbackup@gmx.net>
To: grub-devel@gnu.org
Cc: <schierlm@gmx.de>
Subject: Re: grub-mkrescue: Problem with MBR partition table at start of EFI partition
Date: Sat, 11 May 2019 22:39:25 +0200 [thread overview]
Message-ID: <18486678566337361976@scdbackup.webframe.org> (raw)
In-Reply-To: <20190511191301.pgpmmpuyuavd3ock@pelzflorian.localdomain>
Hi,
Florian Pelz wrote:
> I guess this is off-topic and we cannot learn anything about the
> permissibility of mformat -k from Windows?
Yes.
The on-topic conclusion so far is that i cowardly propose to zeroize
the MBR partition table in the mformat result before populating it
by mcopy.
(Code snippets from SYS_AREA_SPARC around line 855 could be transplanted
and adapted to zeroize bytes 446 to 509 of efiimgfat.)
Exploring the other differences between mformat with and without -k is
probably useless, because the big truck makes its own lane anyway.
Have a nice day :)
Thomas
next prev parent reply other threads:[~2019-05-11 20:41 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-21 13:43 grub-mkrescue: Problem with MBR partition table at start of EFI partition Thomas Schmitt
2019-04-21 17:30 ` Vladimir 'phcoder' Serbinenko
2019-04-21 19:29 ` Thomas Schmitt
2019-04-24 20:32 ` Daniel Kiper
2019-04-25 6:00 ` pelzflorian (Florian Pelz)
2019-04-25 8:18 ` Thomas Schmitt
2019-04-25 9:36 ` pelzflorian (Florian Pelz)
2019-04-30 23:42 ` Vladimir 'phcoder' Serbinenko
2019-05-01 7:33 ` Thomas Schmitt
2019-05-09 20:21 ` Chris Murphy
2019-05-09 21:21 ` Thomas Schmitt
2019-05-10 6:21 ` Thomas Schmitt
2019-05-10 7:09 ` Thomas Schmitt
2019-05-10 12:12 ` pelzflorian (Florian Pelz)
2019-05-10 13:46 ` Thomas Schmitt
2019-05-10 16:12 ` pelzflorian (Florian Pelz)
2019-05-10 16:27 ` Thomas Schmitt
2019-05-11 10:51 ` pelzflorian (Florian Pelz)
2019-05-11 12:05 ` Thomas Schmitt
2019-05-11 14:20 ` pelzflorian (Florian Pelz)
2019-05-11 17:31 ` Thomas Schmitt
2019-05-11 19:13 ` pelzflorian (Florian Pelz)
2019-05-11 20:39 ` Thomas Schmitt [this message]
2019-05-13 21:04 ` Daniel Kiper
2019-05-13 21:55 ` Thomas Schmitt
2019-05-14 6:04 ` Thomas Schmitt
2019-05-15 9:45 ` Daniel Kiper
2019-05-15 10:57 ` Thomas Schmitt
2019-05-16 10:29 ` Daniel Kiper
2019-05-16 12:18 ` Thomas Schmitt
2019-05-20 12:35 ` Daniel Kiper
2019-05-20 14:37 ` Thomas Schmitt
2019-06-15 0:15 ` Chris Murphy
2019-06-15 6:01 ` pelzflorian (Florian Pelz)
2019-05-09 19:51 ` Chris Murphy
2019-05-09 21:06 ` Thomas Schmitt
-- strict thread matches above, loose matches on Subject: below --
2019-05-11 18:15 Michael Schierl
2019-05-11 19:42 ` Thomas Schmitt
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=18486678566337361976@scdbackup.webframe.org \
--to=scdbackup@gmx.net \
--cc=grub-devel@gnu.org \
--cc=schierlm@gmx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.