[arch-releng] [arch-install-scripts] [PATCH] common: mount efivarfs if possible, but don't bail out if it fails

[Thomas Bächler]

Am 15.11.2013 16:31, schrieb Dave Reisner:
> What makes this mount so special that we should avoid failing if it doesn't
> mount? Why would it be any more or less prone to failure if it was
> successfully mounted in the host?

Nobody says that it was mounted on the host.

When a recent kernel boots in EFI mode, it always creates the directory
/sys/firmware/efi/efivars/, regardless whether support for efivarfs was
configured in the kernel (see drivers/firmware/efi/efi.c).

That means that we might have the directory and the mount will still
always fail. Anyway, failing to mount efivarfs should not prevent you
from using arch-chroot, as it only prevents you from manipulating efi
variables, but not from performing other important tasks.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 901 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.archlinux.org/pipermail/arch-releng/attachments/20131115/240f0b04/attachment.asc>