From: "Canek Peláez Valdés" <caneko@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] gummibootx64.efi OR bootx64.efi?
Date: Mon, 2 Mar 2015 01:41:19 -0600 [thread overview]
Message-ID: <CADPrc83KWTkOFy9WhsTMSS42r1GEEV_7HAMDim19RZAq34PJVA@mail.gmail.com> (raw)
In-Reply-To: <20150302001151.51160896ba0a4853a7a4a4c4@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 987 bytes --]
On Sun, Mar 1, 2015 at 11:11 PM, German <gentgerman@gmail.com> wrote:
>
> Out of curiosity I looked into my /boot partition and found two .efi
files. One is /boot/efi/gummiboot/gummibootx64.efi and another is
/boot/efi/boot/bootx64.efi. I remember I've created
/boot/efi/boot/bootx64.efi during install by copying kernel image file to
it and supposedly it was for efibootmng. I think gummiboot has created its
own gummibootx64.efi. Is that safe to delete */boot/bootx64.efi? Thanks
They are the same image; do an md5sum of both, you'll see that they have
the same checksum.
I believe Boot/BOOTX64.EFI is the default location where the "BIOS" (or
whatever is called in UEFI systems) looks for an image to boot,
and gummiboot/gummibootx64.efi is just a copy. I'm not sure, but I would
not delete it: gummiboot creates both copies of the file.
Regards.
--
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México
[-- Attachment #2: Type: text/html, Size: 1137 bytes --]
next prev parent reply other threads:[~2015-03-02 7:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 5:11 [gentoo-user] gummibootx64.efi OR bootx64.efi? German
2015-03-02 6:47 ` Fernando Rodriguez
2015-03-02 7:10 ` German
2015-03-02 7:41 ` Canek Peláez Valdés [this message]
2015-03-02 8:03 ` German
2015-03-02 8:10 ` Canek Peláez Valdés
2015-03-02 8:18 ` German
2015-03-02 8:26 ` Canek Peláez Valdés
2015-03-02 8:27 ` German
2015-03-02 8:31 ` Canek Peláez Valdés
2015-03-02 8:48 ` German
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=CADPrc83KWTkOFy9WhsTMSS42r1GEEV_7HAMDim19RZAq34PJVA@mail.gmail.com \
--to=caneko@gmail.com \
--cc=gentoo-user@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox