similar to: Use .xz (LZMA) for posting releases?

Displaying 20 results from an estimated 1000 matches similar to: "Use .xz (LZMA) for posting releases?"

2012 Apr 26
7
Syslinux 4.10-pre20
I think I finally have nailed down the problems with TFTP on the 4.10 branch, and so I have released 4.10-pre20. Please let me know if you have hardware on which 4.05/4.06-pre3 works, and 4.10-pre20 does not. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.
2013 Jul 04
5
Syslinux 5.11-pre7 not working
Hi, I am a happy user of version 4.06 and have been hoping to upgrade the 5.x series (for the HTTP bits). I have the following problems with the 5.11-pre7 build: 1. TFTP load is horribly slow ... even when the two REAL machines are connected to the same switch. For a typical RHEL installation, the vmlinuz loads ... the initrd.img loads very very slowly and just times out (I waited over 10 mins)
2013 Jul 04
2
Syslinux 5.11-pre7 not working
-------------------------------------------- On Thu, 7/4/13, Matt Fleming <matt at console-pimps.org> wrote: Subject: Re: [syslinux] Syslinux 5.11-pre7 not working To: "Shantanu Gadgil" <shantanugadgil at yahoo.com> Cc: syslinux at zytor.com Date: Thursday, July 4, 2013, 4:51 PM On Wed, 03 Jul, at 11:22:27PM, Shantanu Gadgil wrote: > Hi, > > I am a happy
2014 Aug 11
2
testing out 6.03 network booting... (6.03-pre19)
On 08/11/2014 06:12 AM, Shantanu Gadgil wrote: > Hi all, > > I too am getting positive results using 6.03-pre19 lpxelinux.0, for the problem that I have been facing. > > The symptom was that booting hangs on client side. > On the server (DNSMasq TFTP) it keeps getting a request for the same (MAC address) file. > OR, alternatively it just stops completely. > > My
2013 Oct 21
1
Syslinux 5.11-pre7 not working
-------------------------------------------- On Sun, 10/20/13, Gene Cumm <gene.cumm at gmail.com> wrote: Shantanu, could you please try v6.02?? Your scenario failed on my OptiPlex 760 but with 6.02, it works. See also http://bugzilla.syslinux.org/show_bug.cgi?id=19 Nope, still no joy on the physical machines. Different symptoms though. On the physical machines: The HTTP starts
2012 May 03
1
test message
Test message to see if something is wrong with the mailing list! Regards, Shantanu
2014 Jul 14
1
[syslinux:master] PXE ISR: Force polling on select hardware WORKAROUND
Hi all, Based on the commitdiff comments, this looks like what I (and many many others) have been plagued with. Machines typically affected: DELL PowerEdge 2950, R720, R810, etc. (server class) DELL PowerEdge 960 (desktop class) Eagerly awaiting the next pre-release to test this out! : thumbs up : : thumbs up : Regards, Shantanu
2012 Jun 04
3
Syslinux 4.10-pre20
--- On Thu, 5/31/12, Geert Stappers <stappers at stappers.nl> wrote: > > P.S. > > As usual, eagerly (and patiently) waiting for the HTTP > bits to start > > working properly! ;) :) > > How should I read that??.? Does it mean "I'm waiting to > get time to test" > or do you mean "tested, it doesn't work yet"??? > Anyway, please
2010 Mar 02
2
chain.c32 "Chainboot failed!"
Hi, I am using syslinux-4.00-pre24, -pre27 and -pre31. chain.c32 fails for pre27 and pre31 for particular configs ... shown below. 1) works on pre24, fails with error message "Chainboot failed!" for pre27 and pre31 LABEL local MENU DEFAULT MENU LABEL Local Boot ... (skip PXE boot) KERNEL chain.c32 APPEND hd0 0 2) works on all three. LABEL local
2013 Jul 05
0
Syslinux 5.11-pre7 not working
On Thu, Jul 4, 2013 at 10:44 AM, Shantanu Gadgil <shantanugadgil at yahoo.com> wrote: > On Thu, 7/4/13, Matt Fleming <matt at console-pimps.org> wrote: > > Subject: Re: [syslinux] Syslinux 5.11-pre7 not working > To: "Shantanu Gadgil" <shantanugadgil at yahoo.com> > Cc: syslinux at zytor.com > Date: Thursday, July 4, 2013, 4:51 PM > > On
2014 Aug 15
3
testing out 6.03 network booting... (6.03-pre19)
> > We are not ready for "prime-time" though. > Using the "lpxelinux.0" file from 6.03-pre19 ... > > My RHEL5 installs, when using the "http://" for kernel, initrd and append lines, seem to be hitting some sort of parameter length limit. > The culprit seems to be the long "append" line. > > The same append line, when NOT using
2009 Sep 14
1
[PATCH] xen-unstable: Add bzip2 and lzma/xz libs to stubdom for pvgrub
Hello, The attached patch adds bzip2 and lzma/xz libs to stubdom for pvgrub. This is the first step of getting the additional compression methods supported in pvgrub. There''s still some Makefile voodoo to sort out before pvgrub actually properly gets linked against these new libs. This patch only adds the libs and makes them build. -- Pasi
2014 May 06
0
on High Load using IMAPSYNC : Panic: file ostream-lzma.c: line 147: unreached. Dovecot 2.2.12 with zlib/XZ compression
when syncing Mailboxes with IMAPSYNC, using xz compression the dbox file gets corrupted. the same configuration was working ok on low load with xz compression. Dovecot Version 2.2.12 Linux Mint 16 EXT4 Filesystem another dovecot user already reported the same problem on the mailinglist, using dsync. That user switched to bz2 compression what worked for him. the answer was : > are you on
2014 May 06
1
WG: on High Load using IMAPSYNC : Panic: file ostream-lzma.c: line 147: unreached. Dovecot 2.2.12 with zlib/XZ compression
when syncing Mailboxes with IMAPSYNC, using xz compression the dbox file gets corrupted. the same configuration was working ok on low load with xz compression. Dovecot Version 2.2.12 Linux Mint 16 EXT4 Filesystem another dovecot user already reported the same problem on the mailinglist, using dsync. That user switched to bz2 compression what worked for him. the answer was : > are you on
2014 Aug 14
0
testing out 6.03 network booting... (6.03-pre19)
-------------------------------------------- On Mon, 8/11/14, H. Peter Anvin <hpa at zytor.com> wrote: Subject: Re: [syslinux] testing out 6.03 network booting... (6.03-pre19) To: "Shantanu Gadgil" <shantanugadgil at yahoo.com>, "syslinux at zytor.com" <syslinux at zytor.com> Date: Monday, August 11, 2014, 10:21 PM On 08/11/2014 06:12 AM, Shantanu
2014 Mar 28
1
Panic: file ostream-lzma.c: line 147: unreached. Dovecot 2.2.12 with zlib/XZ compression
While migrating users from Cyrus IMAP v2.3.14 to Dovecot 2.2.12 (compiled from source) dsync aborts with a backtrace on some (maybe 15 out of 800) mail accounts: (same error happens wiht or without -f flag) dsync -D -v -o mail_fsync=never mirror -f -R -u user at domain imapc: <snip> dsync(user at domain.com): Debug: brain M: in state=sync_mails dsync(user at domain.com): Debug: brain M:
2014 May 28
1
PXELINUX problems with 6.03-pre12
Hi, I have been using 6.03-pre11 lpxelinux.0 to deliver standard (TFTP) and HTTP based vmlinuz and kernel images. Things are working fine. When I upgraded the same to 6.03-pre12 it stopped working. On the console of the machine that is booting, is stalls infinitely at the line: PXELINUX 6.03 lwIP 6.03-pre12 Copyright (C) 1994-2014 H. Peter Anvin et al Screen shot attached. FWIW: 1. the
2013 May 16
1
Syslinux 5.x and VMware ESXi mboot.c32
Hi, I have had a VMware ESXi network boot setup for quite some time now. After upgrading from 4.06 to 5.01 (or 5.10-pre3) the network boot fails with the following error: --- snip --- Failed to load COM32 file esxi/5.1.0/mboot.c32 boot: --- snip --- This error is seen for the ESXi bootup only. The default mboot.c32 from syslinux itself doesn't work and this setup has been working with
2014 Aug 09
2
testing out 6.03 network booting...
> -----Original Message----- > From: Matt Fleming [mailto:matt at console-pimps.org] > Sent: 09 July 2014 19:50 > Hey Andrew, > Sorry for the delay. Could you provide the packet dumps of the network > traffic involved in the failed EFI boot? > Hopefully that will allow us to track down exactly what's going wrong. Hi Matt, Appears to all be working under 6.03-pre19 on
2014 Aug 11
0
testing out 6.03 network booting... (6.03-pre19)
Hi all, I too am getting positive results using 6.03-pre19 lpxelinux.0, for the problem that I have been facing. The symptom was that booting hangs on client side. On the server (DNSMasq TFTP) it keeps getting a request for the same (MAC address) file. OR, alternatively it just stops completely. My server: OptiPlex 755. BIOS A22 The PXE booting client: OptiPlex 960. BIOS A17 * Things are