Re: bootctl: no entry could be determined as default (Was: Upgrade to F30 gone wrong)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

> That only works properly on distros that implement the boot loader
> spec and the boot loader interface properly:
>
> https://systemd.io/BOOT_LOADER_SPECIFICATION
> https://systemd.io/BOOT_LOADER_INTERFACE

Thanks for the links, I looked briefly when you replied but figured
I'd need a quiet setup since this is unfamiliar territory. I have
finally read both documents, and they are very accessible even to
someone without prior knowledge.

> Unfortunately, Fedora/grub do not support either.
>
> (Which is a pity of course, since it also means there's no working
> "systemctl --boot-loader-entry=" support in Fedora, nor "sytemctl
> kexec" support).

I see. Do I understand from reading the specification that it was put
together during the Fedora 18 days? Do I understand from reading the
boot loader interface documented that systemd supported all this in
the f18 days too?

Thanks,
Dridi
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux