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 02:26:39 -0600 [thread overview]
Message-ID: <CADPrc82edfDc2235kuS6X23WbKf+RSsoB9NPe77i-k6fSekY6w@mail.gmail.com> (raw)
In-Reply-To: <20150302031818.fcd2e09cc296a263cf533b72@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2550 bytes --]
On Mon, Mar 2, 2015 at 2:18 AM, German <gentgerman@gmail.com> wrote:
>
> On Mon, 2 Mar 2015 02:10:33 -0600
> Canek Peláez Valdés <caneko@gmail.com> wrote:
>
> > On Mon, Mar 2, 2015 at 2:03 AM, German <gentgerman@gmail.com> wrote:
> > >
> > > On Mon, 2 Mar 2015 01:41:19 -0600
> > > Canek Peláez Valdés <caneko@gmail.com> wrote:
> > >
> > > > 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.
> > >
> > > Well, no, I have created */boot/bootx64.efi manually and
> > */gummiboot/gummibootx64.efi was created by gummiboot install.
> >
> > In my machines boot/bootx64.efi was created by gummiboot, and it's the
same
> > ile as gummiboot/gummibootx64.efi (same checksum).
> >
> > What does bootctl says?
>
> bootctl: command not found. How to use bootctl?
Sorry, my bad; bootctl comes with systemd. I thought it came with gummiboot.
However, "gummiboot status" shows almost the same information. In my case:
Boot Loader Binaries:
ESP: /dev/disk/by-partuuid/b4abf4dc-abfc-45c5-b356-30db1e0b15b3
File: └─/EFI/gummiboot/gummibootx64.efi (gummiboot 45)
File: └─/EFI/Boot/BOOTX64.EFI (gummiboot 45)
Boot Loader Entries in EFI Variables:
Title: UEFI OS
ID: 0x0001
Status: active, boot-order
Partition: /dev/disk/by-partuuid/b4abf4dc-abfc-45c5-b356-30db1e0b15b3
File: └─/EFI/BOOT/BOOTX64.EFI
As you can see, Boot/BOOTX64.EFI is actually gummiboot.
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: 3506 bytes --]
next prev parent reply other threads:[~2015-03-02 8:27 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
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 [this message]
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=CADPrc82edfDc2235kuS6X23WbKf+RSsoB9NPe77i-k6fSekY6w@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