Re: Syslinux in stretch-backports (Re: syslinux_6.04~git20171011.af7e95c3+dfsg1-4~bpo9+1_amd64.changes is NEW)
Hallo Carl, thx for the pointer. I fit in the group described with "conditions when you might want to consider using it" ;-) A feature I missed is "chainload". I wanted to chainload grub2, just to give it a try. "As I write (summer, 2018), the latest version is 6.0.3, and has not been updated since 2014, so it's beginning to look like it's been abandoned. " Looking at the git repo proves this comment wrong: https://repo.or.cz/syslinux.git/shortlog Obviously the author missed the 6.0.4 release (which has not been published in the news section of the syslinux homepage) Of course, grub's commit log looks much more impressive: http://git.savannah.gnu.org/cgit/grub.git/log/ Ingo Am 14.11.2018 um 17:09 schrieb Carl Karsten: > On Tue, Oct 23, 2018 at 11:32 AM Ingo Wichmann wrote: >> >> Hi Steve, >> >> Am 23.10.2018 um 15:04 schrieb Holger Levsen: >> Wow. I'm surprised to hear anybody is actually really using syslinux with UEFI! I'm curious why, rather than grub - can you share? >> >> I've got a working setup with pxelinux. And I don't want to maintain a >> grub and a syslinux configuration, both. Most distros ship with isolinux >> as bootloader on the installer image. So it's easy to copy and paste the >> configuration to get the installer running on PXE. >> >> So until now I don't see any advantages moving to GRUB. Where do you see >> advantages in using GRUB for PXE? > > I just read most of these pages, which have sections like: "When to > Use SYSLINUX" and "Conditions in which GRUB 2 may not be the best > choice..." > http://www.rodsbooks.com/efi-bootloaders/syslinux.html > Originally written: 6/30/2013; last update: 7/7/2018 > > It is the best writeup I have seen on the pros n cons of all the boot > manager/loader options, and very up to date. > > my summary: "It depends" ;) > > I think the best choice for "this" is to follow the default of the > base os install, which is currently grub 2. if someday that changes, > then we should migrate all the things. > > Similar to using the same linux kernel on the installer and the installed os. > > > > >> >> Ingo >> >>> >>> Ingo (in cc:) told me: >>> >>> --begin-- >>> With the version in stretch I was able to boot the Debian and Ubuntu >>> installers. But not the Centos and SuSE installers: >>> 51M centos7_64/initrd.img >>> 45M ubuntu1804_64/initrd.gz >>> 24M debian9_64/initrd.gz >>> 93M suse15_64/initrd >>> >>> Here I found a hint, that version 6.03 of syslinux has several issues >>> affecting both UEFI and PXE: >>> https://serverfault.com/questions/810226/syslinux-how-to-correctly-configure-for-uefi-pxe-boot#answers >>> --end-- >>> >>> >> >> -- >> Linuxhotel GmbH, Geschäftsführer Dipl.-Ing. Ingo Wichmann >> HRB 20463 Amtsgericht Essen, UStID DE 814 943 641 >> Antonienallee 1, 45279 Essen, Tel.: 0201 8536-600, http://www.linuxhotel.de >> > > -- Linuxhotel GmbH, Geschäftsführer Dipl.-Ing. Ingo Wichmann HRB 20463 Amtsgericht Essen, UStID DE 814 943 641 Antonienallee 1, 45279 Essen, Tel.: 0201 8536-600, http://www.linuxhotel.de
Re: Syslinux in stretch-backports (Re: syslinux_6.04~git20171011.af7e95c3+dfsg1-4~bpo9+1_amd64.changes is NEW)
On Tue, Oct 23, 2018 at 11:32 AM Ingo Wichmann wrote: > > Hi Steve, > > Am 23.10.2018 um 15:04 schrieb Holger Levsen: > > >> Wow. I'm surprised to hear anybody is actually really using syslinux > >> with UEFI! I'm curious why, rather than grub - can you share? > > I've got a working setup with pxelinux. And I don't want to maintain a > grub and a syslinux configuration, both. Most distros ship with isolinux > as bootloader on the installer image. So it's easy to copy and paste the > configuration to get the installer running on PXE. > > So until now I don't see any advantages moving to GRUB. Where do you see > advantages in using GRUB for PXE? I just read most of these pages, which have sections like: "When to Use SYSLINUX" and "Conditions in which GRUB 2 may not be the best choice..." http://www.rodsbooks.com/efi-bootloaders/syslinux.html Originally written: 6/30/2013; last update: 7/7/2018 It is the best writeup I have seen on the pros n cons of all the boot manager/loader options, and very up to date. my summary: "It depends" ;) I think the best choice for "this" is to follow the default of the base os install, which is currently grub 2. if someday that changes, then we should migrate all the things. Similar to using the same linux kernel on the installer and the installed os. > > Ingo > > > > > Ingo (in cc:) told me: > > > > --begin-- > > With the version in stretch I was able to boot the Debian and Ubuntu > > installers. But not the Centos and SuSE installers: > > 51M centos7_64/initrd.img > > 45M ubuntu1804_64/initrd.gz > > 24M debian9_64/initrd.gz > > 93M suse15_64/initrd > > > > Here I found a hint, that version 6.03 of syslinux has several issues > > affecting both UEFI and PXE: > > https://serverfault.com/questions/810226/syslinux-how-to-correctly-configure-for-uefi-pxe-boot#answers > > --end-- > > > > > > -- > Linuxhotel GmbH, Geschäftsführer Dipl.-Ing. Ingo Wichmann > HRB 20463 Amtsgericht Essen, UStID DE 814 943 641 > Antonienallee 1, 45279 Essen, Tel.: 0201 8536-600, http://www.linuxhotel.de > -- Carl K
Re: Syslinux in stretch-backports (Re: syslinux_6.04~git20171011.af7e95c3+dfsg1-4~bpo9+1_amd64.changes is NEW)
Hi Steve, Am 23.10.2018 um 15:04 schrieb Holger Levsen: >> Wow. I'm surprised to hear anybody is actually really using syslinux >> with UEFI! I'm curious why, rather than grub - can you share? I've got a working setup with pxelinux. And I don't want to maintain a grub and a syslinux configuration, both. Most distros ship with isolinux as bootloader on the installer image. So it's easy to copy and paste the configuration to get the installer running on PXE. So until now I don't see any advantages moving to GRUB. Where do you see advantages in using GRUB for PXE? Ingo > > Ingo (in cc:) told me: > > --begin-- > With the version in stretch I was able to boot the Debian and Ubuntu > installers. But not the Centos and SuSE installers: > 51M centos7_64/initrd.img > 45M ubuntu1804_64/initrd.gz > 24M debian9_64/initrd.gz > 93M suse15_64/initrd > > Here I found a hint, that version 6.03 of syslinux has several issues > affecting both UEFI and PXE: > https://serverfault.com/questions/810226/syslinux-how-to-correctly-configure-for-uefi-pxe-boot#answers > --end-- > > -- Linuxhotel GmbH, Geschäftsführer Dipl.-Ing. Ingo Wichmann HRB 20463 Amtsgericht Essen, UStID DE 814 943 641 Antonienallee 1, 45279 Essen, Tel.: 0201 8536-600, http://www.linuxhotel.de signature.asc Description: OpenPGP digital signature
Re: Syslinux in stretch-backports (Re: syslinux_6.04~git20171011.af7e95c3+dfsg1-4~bpo9+1_amd64.changes is NEW)
Hi, On Sat, Oct 13, 2018 at 07:37:14PM +0100, Steve McIntyre wrote: > >On Fri, Oct 12, 2018 at 09:32:13PM +0200, Lukas Schwaighofer wrote: > >> thanks for uploading syslinux to backports. Was there a specific reason > >> for that I should be aware of? > >a customer asked for it, claiming several problems with UEFI. > Wow. I'm surprised to hear anybody is actually really using syslinux > with UEFI! I'm curious why, rather than grub - can you share? Ingo (in cc:) told me: --begin-- With the version in stretch I was able to boot the Debian and Ubuntu installers. But not the Centos and SuSE installers: 51M centos7_64/initrd.img 45M ubuntu1804_64/initrd.gz 24M debian9_64/initrd.gz 93M suse15_64/initrd Here I found a hint, that version 6.03 of syslinux has several issues affecting both UEFI and PXE: https://serverfault.com/questions/810226/syslinux-how-to-correctly-configure-for-uefi-pxe-boot#answers --end-- -- cheers, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
Re: Syslinux in stretch-backports (Re: syslinux_6.04~git20171011.af7e95c3+dfsg1-4~bpo9+1_amd64.changes is NEW)
On Sat, Oct 13, 2018 at 07:37:14PM +0100, Steve McIntyre wrote: > Wow. I'm surprised to hear anybody is actually really using syslinux > with UEFI! I'm curious why, rather than grub - can you share? the pxelinux package seems to be whats really wanted. -- cheers, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
Re: Syslinux in stretch-backports (Re: syslinux_6.04~git20171011.af7e95c3+dfsg1-4~bpo9+1_amd64.changes is NEW)
On Sat, Oct 13, 2018 at 05:38:14PM +, Holger Levsen wrote: >Hi Lukas, > >On Fri, Oct 12, 2018 at 09:32:13PM +0200, Lukas Schwaighofer wrote: >> thanks for uploading syslinux to backports. Was there a specific reason >> for that I should be aware of? > >a customer asked for it, claiming several problems with UEFI. Wow. I'm surprised to hear anybody is actually really using syslinux with UEFI! I'm curious why, rather than grub - can you share? Cheers, Steve -- Steve McIntyre, Cambridge, UK.st...@einval.com The two hard things in computing: * naming things * cache invalidation * off-by-one errors -- Stig Sandbeck Mathisen
Re: Syslinux in stretch-backports (Re: syslinux_6.04~git20171011.af7e95c3+dfsg1-4~bpo9+1_amd64.changes is NEW)
Hi Lukas, On Fri, Oct 12, 2018 at 09:32:13PM +0200, Lukas Schwaighofer wrote: > thanks for uploading syslinux to backports. Was there a specific reason > for that I should be aware of? a customer asked for it, claiming several problems with UEFI. > Heads up: I plan to upload a new version of syslinux on the weekend. > With the just uploaded gnu-efi 3.0.8 [2], syslinux needs a patch as it > otherwise FTBFS. So with the next version depending on gnu-efi >= > 3.0.8, keeping syslinux up to date in backports might become tricky > very soon. gnu-efi seems to be pretty straightforward to backport, so I don't think this will be particularily tricky. -- cheers, Holger --- holger@(debian|reproducible-builds|layer-acht).org PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C signature.asc Description: PGP signature
