On 07/05/2017 08:36 PM, Jude DaShiell wrote: > That's not a package I specifically installed, but may have been > pulled in by another package dependency. I'll check for the package > and remove it if found. since systemd-boot is included with systemd maybe it just complains whether you're using it or not but doesn't stop the systemd upgrade? i haven't noticed it in the terminal, but that doesn't mean it didn't happen. > On Wed, 5 Jul 2017, Eli Schwartz via arch-general wrote: > >> Date: Wed, 5 Jul 2017 15:21:31 >> From: Eli Schwartz via arch-general <arch-general@xxxxxxxxxxxxx> >> To: arch-general@xxxxxxxxxxxxx >> Cc: Eli Schwartz <eschwartz93@xxxxxxxxx> >> Subject: Re: systemd on bios computer >> >> On 07/04/2017 02:52 PM, Jude DaShiell wrote: >>> When doing a systemd upgrade I get: >>> (3/7) Upgrading systemd-boot... >>> Couldn't find EFI system partition. It is recommended to mount it to >>> /boot. Alternatively, use --path= to specify path to mount point. >>> error: command failed to execute correctly >>> Are either of the above alternatives even viable for a real bios >>> machine? >>> This one got built when efi was somewhere on the drawing board or maybe >>> before efi ever got to the drawing board. >> >> Sounds like you have the AUR package "systemd-boot-pacman-hook" >> installed, which automatically runs `/usr/bin/bootctl update` after >> every update of the systed package. >> >> *Why* do you have that installed on a BIOS machine? This command is only >> relevant for people who are using systemd-boot as their boot manager on >> a computer that uses UEFI, and the error message is quite right in >> saying that it cannot find an EFI System Partition for UEFI booting... >> on a machine that boots via BIOS rather than UEFI. >> >> > -- Information Technology Works https://ITwrx.org @ITwrxorg
