Re: broken link /etc/extlinux.conf in syslinux-extlinux because /boot/extlinux/extlinux.conf is missing

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

 



On Tue, 23 Aug 2022 19:45:24 +0200
"Walter H. via users" <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

> https://bugzilla.redhat.com/show_bug.cgi?id=1016304 ; <-- still
> relevant for fc36(!)
> 
> Why?

I think the answer is that no one has done the work.  It has been a
long time since I had anything to do with syslinux.  From reading at
this link,
https://wiki.syslinux.org/wiki/index.php?title=Config
it was contemporary with lilo as the main bootloader, but for booting
install media (including floppies, where I recall it from). I thought it
might be obsolete because of its age, but it turns out that there are
several packages that are dependent on it (I used dnf to try to remove
it, and there they were).

After perusing the link above a little, I think that any default
extlinux.conf file in /boot/extlinux/ would be incorrect, as it needs
the location of the kernel and the kernel options added [1], and they
need to be relative to the file system on the media. Anyway, at the
link above there is a sample extlinux.conf that you could try, after
putting in the kernel you actually want to boot, and the kernel options
you want to use.  If it works, you could then update the ticket with
that information, and the extlinux.conf file that worked, so that it
could be added to the package if there is a kind soul willing to do the
work. Or, since they will likely be more knowledgeable than I am, they
might be able to explain why it wouldn't work.

1. This could be automated by changing grubby so that when a new kernel
is installed, the options are added to /boot/extlinux/extlinux.conf the
same way they are to the boot stanzas in /boot/loader/entries.  But that
again requires someone to do the work.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-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/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux