Re: Upgrade syslinux to 4.04-pre14 or wait for 4.04?
"Gilles Espinasse" <[email protected]>
| Newsgroups | gmane.comp.security.ipcop.devel |
|---|---|
| Message-ID | <002001cbef70$390b2b40$f9b5a8c0@pii350> |
----- Original Message ----- From: "Olaf Westrik" <weizen_42-Yz37vSk3/[email protected]> To: "Gilles Espinasse" <[email protected]> Cc: "IPCOP devel" <[email protected]> Sent: Wednesday, March 30, 2011 8:30 AM Subject: Re: [IPCop-devel] Upgrade syslinux to 4.04-pre14 or wait for 4.04? > On 2011-03-29 14:18, Gilles Espinasse wrote: > > 4.03 is know to have some issues with some bios at boot. > > Last call before 4.04 release has been made 15 day ago. In that time > > 4.04-pre14 prebuild binaries has been found to be badly compiled (by a new > > compiler). > > > > Recompiling 4.04-pre14 should work (just compiled, not yet run) > > I have fixed a issue recompiling the gpxe part that was not supporting our > > pie by default gcc. > > Should I commit the 4.03 =>4.04-pre14 upgrade? > > I think we can wait for 4.04. > > 1.9.17 has syslinux 3.86, .18/.19 will install with 4.03. > If we leave syslinux 4.03 out of the .18/.19 update package, anyone with > problems installing .19 should be able to install .17 and upgrade using > normal mechanisms. > > If the compile problems are sorted, we can update syslinux to 4.04. > > > Is that OK for you? > > > Olaf That could be ok too. Anyway pre14 recompilation should be only better than pre14 prebuild code as I was able to boot. The 4.03 bios issue should not be that current and we still have some work after 1.9.18/1.9.19 release. It is just that 4.03 has other issue (one fix for isohybrid), so that make not much sense for me to work at isohybrid with a 4.03 base code. Kernel merge windows is closed so HPA may have a bit more time for syslinux. I had think the 4.04 release would be fast, but I don't know due to the linker issue with pre13 and pre14. I have booted with my compiled 4.04-pre14 but had one issue during configuration after install. The case is when I configured with one pci card found as green and one isa card as static. Selection work nicely, but address configuration fail a bit later with cp: can't stat '/etc/dhcp-*params': No such file or directory Segmentation fault That fail in that case in the first card address configuration (green). That does not happen when using 2 pci cards (and red as static). I have to look at the address setup code. Gilles ------------------------------------------------------------------------------ Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf