FS#21790 - [syslinux] add install/upgarde message - for extlinux users
Attached to Project:
Arch Linux
Opened by Matthew Gyurgyik (pyther) - Monday, 22 November 2010, 18:31 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 17 August 2011, 12:17 GMT
Opened by Matthew Gyurgyik (pyther) - Monday, 22 November 2010, 18:31 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 17 August 2011, 12:17 GMT
|
Details
A post_install() and post_upgrade() message should be
added...
post_install() { echo " * EXTLINUX Users:" echo " * see http://wiki.archlinux.org/index.php/Syslinux" } post_upgrade() { echo " * EXTLINUX Users:" echo " * Copy updated *.c32 files from /usr/lib/syslinux to /boot/syslinux" echo " * Run extlinux --upgrade" } The wiki provides useful information about installing and configuring syslinux. On post_upgrade() we should remind users to copy updated files from /usr/lib/syslinux to /boot/syslinux, since extlinux --upgrade does not do this. While we are at it, we should give them a friendly reminder to run extlinux --upgrade |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Wednesday, 17 August 2011, 12:17 GMT
Reason for closing: Won't fix
Wednesday, 17 August 2011, 12:17 GMT
Reason for closing: Won't fix
Comment by Jan de Groot (JGC) -
Tuesday, 23 November 2010, 11:26 GMT
Comment by
Matthew Gyurgyik (pyther) - Tuesday,
23 November 2010, 14:16 GMT
I don't agree with the post_install message, as people who install
syslinux for that reason should be able to find documentation
about it themselves (chances are they're installing it because the
documentation says so). For the post_upgrade thing: AFAIK we don't
do that with grub, but we do it with lilo. For lilo, not
re-running lilo breaks booting. For grub, it doesn't matter if you
update the bootloader in /boot or not. If extlinux doesn't break
by not copying those files and upgrading extlinux, then we should
not have to print that boot message.
Good point. Thinking about it nothing should break on an upgrade.
Even if the com32 modules are linked into /boot they should be
"applications". I would have to imagine an older version of
syslinux would be able to load the the com32 modules, unless if
there is a major change in the syslinux code.