search for: pre1s

... > nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \ > -DHEXDATE="0x56dc3c62" \ > -Di386 \ > -I/tmp/syslinux-6.04-pre1/core/ \ > -l ldlinux.lsr -o ldlinux.o -MP -MD ./.ldlinux.o.d /tmp/syslinux-6.04-pre1/core/ldlinux.asm > nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \ > -DHEXDATE="0x56dc3c62" \ > -Di386 \ >

On 05.03.2016 14:43, Gene Cumm via Syslinux wrote: > After so much time and improvements, I'm glad to see and publicize a > pre-release, 6.04-pre1 in > https://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/6.04/ > > Personally, I've already been working testing the pre-release as-is > and my tests have been positive so far. I appreciate feedback like > that

On 06.03.2016 18:23, poma wrote: > On 06.03.2016 16:47, poma wrote: >> ... >>> nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \ >>> -DHEXDATE="0x56dc3c62" \ >>> -Di386 \ >>> -I/tmp/syslinux-6.04-pre1/core/ \ >>> -l ldlinux.lsr -o ldlinux.o -MP -MD ./.ldlinux.o.d /tmp/syslinux-6.04-pre1/core/ldlinux.asm >>>

After so much time and improvements, I'm glad to see and publicize a pre-release, 6.04-pre1 in https://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/6.04/ Personally, I've already been working testing the pre-release as-is and my tests have been positive so far. I appreciate feedback like that from Gabriele Balducci and testing "make bios installer". Yes, there are a

On 06.03.2016 16:47, poma wrote: > ... >> nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \ >> -DHEXDATE="0x56dc3c62" \ >> -Di386 \ >> -I/tmp/syslinux-6.04-pre1/core/ \ >> -l ldlinux.lsr -o ldlinux.o -MP -MD ./.ldlinux.o.d /tmp/syslinux-6.04-pre1/core/ldlinux.asm >> nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \

On 07.03.2016 06:45, poma wrote: > On 06.03.2016 18:23, poma wrote: >> On 06.03.2016 16:47, poma wrote: >>> ... >>>> nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \ >>>> -DHEXDATE="0x56dc3c62" \ >>>> -Di386 \ >>>> -I/tmp/syslinux-6.04-pre1/core/ \ >>>> -l ldlinux.lsr -o ldlinux.o -MP -MD

hello everybody, apologies if I'm missing something here Just tried to build 6.04-pre1 test version with: make bios installer and found some problems all (seemingly) related to inaccurate paths in various Makefiles. I enclose a complete patch at the end of this email, which details the problems I found and how they got fixed for me. As an example, this is the first error I got:

Network UPS Tools version 2.2.2-pre1 has been released. http://www.networkupstools.org/ Direct access: - Download: http://www.networkupstools.org/source/2.2/testing/nut-2.2.2-pre1.tar.gz - News: http://www.networkupstools.org/source/2.2/testing/new-2.2.2-pre1.txt - ChangeLog: http://www.networkupstools.org/source/2.2/testing/ChangeLog Arnaud and the NUT team -- Linux / Unix Expert R&D -

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When I tried to use the menu.c32 from SYSLINUX 3.30-pre1, the simple menu have different background color than that in 3.20. 1. use the menu.c32 from SYSLINUX 3.30-pre1, the simple menu is: http://lfod.nchc.org.tw/stick/syslinux/syslinux_menu_3.30_pre1.jpg 2. use the menu.c32 from SYSLINUX 3.20, the simple menu is:

> Thank you all. > > It looks like -mno-red-zone flag is already in master branch since > commit 7d70885d, but it seems it is applied to all EFI builds. Finally we are on the same page. > > IIUC, the problem only affects efi64 builds. Have you actually tested efi32 (ia32) builds? > > So here's the modification of my patch to only apply -mno-red-zone >

On Sun, Dec 2, 2018 at 9:29 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > > > _ target/EFI/BOOT/SYSLINUX.CFG > > > > I don't think that exists? (see list below) > > > In our "first test" (simple boot prompt), we created > "target/EFI/BOOT/SYSLINUX.CFG". In our "second test" we _added_ >

> >> Let me double check what the status of 6.04-pre1 is. Maybe this patch > >> is not necessary at all! > > OK, I have verified beyond doubt that 6.04-pre1 (prebuilt from > kernel.org) indeed does fix the issue on the affected systems. > > Again, sorry for the churn! > > Best Regards, > - Chris OK, so, from the user's point of view, the

The 0.3.6 release will be mostly bug fix oriented. Before releasing, I'd love having more feedback on it. So here come the -pre1 release. I would like to thank the following people for making this new release possible : Pierre for his patches, Gert for his tests, Alexander Andino for his great artwork, Ralf Carl for his very reactive debugging on older hardware, Changelog for -pre1 *

The 0.3.6 release will be mostly bug fix oriented. Before releasing, I'd love having more feedback on it. So here come the -pre1 release. I would like to thank the following people for making this new release possible : Pierre for his patches, Gert for his tests, Alexander Andino for his great artwork, Ralf Carl for his very reactive debugging on older hardware, Changelog for -pre1 *

> Let me double check what the status of 6.04-pre1 is. Maybe this patch > is not necessary at all! Just a reminder: _ 6.04-pre1 can be downloaded from kernel.org, and it includes pre-built binaries, so no "make" anything is needed (and to some degree, not always recommended). _ In many cases, testing with pre-built official binaries is desired, so others can attempt to

> Now it is just dd, mkfs and copy in the files we need. > One less thing to worry about keeping versions consistent. > > > I just noticed those 2 files that were added by > > > syslinux -i boot.img > > > (right?) > > > > > > Yes, those 2 files came from your 'syslinux' command (in your other > > email). We don't want anything

Hi to all, I am having a problem when using recode from the car package. I have a variable that is char and when I use recode to create a new variable that is supposed to be numeric I get a factor variable. Here is the code I am using: > FCI$PRE1 <- recode (PRE1RES, " c('C', 'c')=1 ; else = 0 ; as.factor.result=FALSE ") So, if I understand correctly the recode

It seems that 2.03-pre1 resolves PXELINUX problem on a reasonable number of hosts. Perhaps somewhat importantly this seems to include the RBFG PXE boot floppy, which did not work with 2.02. This was somewhat of a surprise, since it didn't exhibit the failure mode that I would have thought would have been the trigger of the bug. Instead, it was one of those stacks that would transmit packets

Probably have already seen this, but since I didn't see in the email archives: thune:/usr/src/syslinux/syslinux-2.12-pre1# make install make -C sample com32 all make[1]: Entering directory `/usr/src/syslinux/syslinux-2.12-pre1/sample' make[1]: *** No rule to make target `com32'. Stop. make[1]: Leaving directory `/usr/src/syslinux/syslinux-2.12-pre1/sample' make: *** [installer]

Network UPS Tools version 2.2.1-pre1 has been released. http://www.networkupstools.org/ Note that a transition is underway for both the NUT domain name and the webserver. So you might face few minor problems... USB UPS owners are also warmly welcome to test the shutdown function of their device. Direct access: - Download: http://www.networkupstools.org/source/2.2/testing/nut-2.2.1-pre1.tar.gz