On 02/10/2018 04:27 PM, Stephen Morris wrote:
On 10/2/18 5:46 pm, Samuel Sieb wrote:
On 02/09/2018 09:40 AM, Rick Stevens wrote:
IIRC, /boot/efi/* is created by the initial anaconda install sequence
and is in place in case you use UEFI at some point in the future. Since
it's only about 15MB in size, it's pretty innocuous and I wouldn't
worry about it. Ubuntu's install mechanism isn't the same and it
probably doesn't create that directory unless it notices you are in UEFI
boot mode at the time of install.
What's in yours? Are any of the files owned? Mine is just an empty
directory tree to /boot/efi/EFI/fedora/. I just checked further and
that directory is owned by grub-common, but not the parent directories.
I've just checked my efi directory, and /boot/efi is owned by 'root', as
are directories /boot/efi/EFI and /boot/efi/System and file
/boot/efi/mach_kernel. Drilling a little bit further directories
/boot/efi/EFI/BOOT and /boot/efi/EFI/fedora are also owned by root, as
is directory /boot/efi/System/Library, so I'm assuming everything is.
Sorry for not being more clear. I mean owned in the rpm way. If you do
"rpm -qf /path/to/file" it will tell you which package put the file (or
directory) there.
I'm not concerned so much by the space that structure is using, but more
just querying why it is there, and, if I happen to delete that structure
will that cause any problems, or, if I do delete it is something going
to put it back?
If you don't have an EFI system, then deleting those files shouldn't
make any difference. But I'm curious, since you actually have files in
there, can you check what package owns them as described above?
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
