1 |
On Mon, Mar 2, 2015 at 2:03 AM, German <gentgerman@×××××.com> wrote: |
2 |
> |
3 |
> On Mon, 2 Mar 2015 01:41:19 -0600 |
4 |
> Canek Peláez Valdés <caneko@×××××.com> wrote: |
5 |
> |
6 |
> > On Sun, Mar 1, 2015 at 11:11 PM, German <gentgerman@×××××.com> wrote: |
7 |
> > > |
8 |
> > > Out of curiosity I looked into my /boot partition and found two .efi |
9 |
> > files. One is /boot/efi/gummiboot/gummibootx64.efi and another is |
10 |
> > /boot/efi/boot/bootx64.efi. I remember I've created |
11 |
> > /boot/efi/boot/bootx64.efi during install by copying kernel image file |
12 |
to |
13 |
> > it and supposedly it was for efibootmng. I think gummiboot has created |
14 |
its |
15 |
> > own gummibootx64.efi. Is that safe to delete */boot/bootx64.efi? Thanks |
16 |
> > |
17 |
> > They are the same image; do an md5sum of both, you'll see that they have |
18 |
> > the same checksum. |
19 |
> > |
20 |
> > I believe Boot/BOOTX64.EFI is the default location where the "BIOS" (or |
21 |
> > whatever is called in UEFI systems) looks for an image to boot, |
22 |
> > and gummiboot/gummibootx64.efi is just a copy. I'm not sure, but I would |
23 |
> > not delete it: |
24 |
> |
25 |
> gummiboot creates both copies of the file. |
26 |
> |
27 |
> Well, no, I have created */boot/bootx64.efi manually and |
28 |
*/gummiboot/gummibootx64.efi was created by gummiboot install. |
29 |
|
30 |
In my machines boot/bootx64.efi was created by gummiboot, and it's the same |
31 |
ile as gummiboot/gummibootx64.efi (same checksum). |
32 |
|
33 |
What does bootctl says? |
34 |
|
35 |
Regards. |
36 |
-- |
37 |
Canek Peláez Valdés |
38 |
Profesor de asignatura, Facultad de Ciencias |
39 |
Universidad Nacional Autónoma de México |