FS#21789 - [syslinux] Include Example extlinux.conf file

Attached to Project: Arch Linux
Opened by Matthew Gyurgyik (pyther) - Monday, 22 November 2010, 18:15 GMT
Last edited by Eric Belanger (Snowman) - Sunday, 13 March 2011, 20:36 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

extlinux.conf should be included in the syslinux package to provide an example configuration like grub does

1. The config file will boot the arch entry after 5 seconds
2. If UI menu.c32 or UI vesamenu.c32 is uncommented, but is not in /boot/syslinux, syslinux will give an error, and give the user a prompt

Attachments:
1. Purposed configuration file
2. Screenshot of what the menus (menu.c32 and vesamenu.c32) looks like

   extlinux_example.conf (1.8 KiB)
   textmenu.png (21.3 KiB)
   vesamenu.png (93.2 KiB)
This task depends upon

Closed by  Eric Belanger (Snowman)
Sunday, 13 March 2011, 20:36 GMT
Reason for closing:  Implemented
Additional comments about closing:  syslinux 4.03-4 now includes a default configuration file.
Comment by Matthew Gyurgyik (pyther) - Tuesday, 23 November 2010, 01:02 GMT
After talking to a developer in #syslinux @ freenode.net, we should name the default config file syslinux.cfg

19:31 < pyther> for an example config what would be preferred: extlinux.conf or syslinux.conf
19:32 < hpa> syslinux.cfg probably
19:32 < pyther> not .conf ?
19:32 < hpa> Correct
19:33 < pyther> hpa: is there any written document or rational behind this? I'm trying to get a sample configuration
file in my distro's syslinux package, and I know I'll be asked why .cfg instead of .conf
19:34 < hpa> syslinux.cfg was the original name since the old days when it had to fit in an 8.3 old-style FAT filename
19:35 < hpa> In Syslinux 3, when I first added extlinux, I used a different name, extlinux.conf
19:35 < pyther> and that is there simply for compatibility reasons?
19:36 < hpa> Similarly, iso9660 (isolinux), used isolinux.cfg
19:36 < hpa> Now what I have is: Syslinux/extlinux use extlinux.conf first, then syslinux.cfg; isolinux uses
isolinux.cfg first then syslinux.cfg
19:36 < hpa> So the idea is to use syslinux.cfg unless you want to have *different* instructions for different
filesystems

hpa is a developer for the Syslinux project

It should be noted that syslinux.conf does NOT work
Since version 4 syslinux and extlinux are the same thing
Comment by Matthew Gyurgyik (pyther) - Sunday, 02 January 2011, 23:04 GMT
Made some minor fixes (spelling, wording, etc...) and aligned to text width of 80.
Also commented out all menu related lines.

I think we should offer a bare configuration and let users uncomment the menu stuff if they want to use a menu.
   syslinux_example_config.cfg (1.7 KiB)
Comment by Matthew Gyurgyik (pyther) - Tuesday, 04 January 2011, 22:47 GMT
As per my discussion with Thomas I updated the config

*Default Vesa Menu
*Adds HDT, Reboot, Shutdown Menu enteries
   syslinux_example_config.cfg (2.1 KiB)

Loading...