-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
May be, I asked systemd folks to confirm because this may or may not
be specific to something systemd does internally when modifying them.
I didn't get anything on efibootmgr, and I also didn't try again to
use bootctl install, I just created entries w
On Fri, Aug 14, 2015 at 8:42 PM, Michał Zegan
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello.
>
> I was trying to install archlinux with linux 4.1, systemd-224 on the
> uefi machine.
> At the end of system installation, I issued bootctl install command
> from within chroot, bu
On Fri, 14.08.15 19:42, Michał Zegan (webczat_...@poczta.onet.pl) wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello.
>
> I was trying to install archlinux with linux 4.1, systemd-224 on the
> uefi machine.
> At the end of system installation, I issued bootctl install command
> f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
I was trying to install archlinux with linux 4.1, systemd-224 on the
uefi machine.
At the end of system installation, I issued bootctl install command
from within chroot, but the command has failed because I did not have
access to efi variables