Hi Yes that is what it does. Sorry for the long response. I've been on the road. On Jul 20, 2016 17:11, "Jason White" <jason@xxxxxxxxxxxx> wrote: > > Janina Sajka <janina@xxxxxxxxxxx> wrote: > > A couple specific questions below ... > > > > Alonzo Cuellar writes: > > > ... > > > After that I just configure /boot/loader/entries/arch.conf > > > > > > > > > title Arch Linux > > > linux /vmlinuz-linux > > > initrd /intel-ucode.img > > I didn't have this entry, but I do see the file in the directory. So, I > > added it as you have it. But, I'm curious. What does it do? > > According to the bootctl manual page: > "A copy of systemd-boot will be stored as the EFI default/fallback loader at > /EFI/Boot/boot*.efi. A systemd-boot entry in the EFI boot variables is created > and added to the top of the boot order list." > > I strongly suspect the configuration file, as above, then enables the boot > loader to find the kernel and the initrd. Thus the start-up order is: > > EFI firmware -> boot loader -> kernel. > > and the kernel is not booted directly by the EFI firmware in this > configuration, but by the *.efi boot loader executable specified in the EFI > boot variable. > > _______________________________________________ > Speakup mailing list > Speakup@xxxxxxxxxxxxxxxxx > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup _______________________________________________ Speakup mailing list Speakup@xxxxxxxxxxxxxxxxx http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
