similar to: CESA-2014:0861 Moderate CentOS 6 lzo Update

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

CentOS Errata and Security Advisory 2014:0861 Moderate Upstream details at : https://access.redhat.com/errata/RHSA-2014:0861 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 898c40521dfa677aa2217a083a9f382618b359d7a1a0361167427123f3397632 lzo-2.06-6.el7_0.2.i686.rpm

Hi, I don''t know if this has been discussed before, but have you thought about adding LZO compression to ZFS? One zfs-fuse user has provided a patch which implements LZO compression, and he claims better compression ratios *and* better speed than lzjb. The miniLZO library is licensed under the GPL, but the author specifically says that other licenses are available by request. Has this

Hello, I downloaded tinc 1.0.9 from the site and tried to build on Fedora 10 on i386 (and also x86_64). I get, during the configure phase: checking for zlib.h... yes checking for compress2 in -lz... yes checking for lzo1x_1_compress in -llzo2... no checking for lzo1x_1_compress in -llzo... no configure: error: "lzo libraries not found." but: # rpm -qi lzo Name : lzo

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I've added lzo compression support for tinc 1.0pre8. Lzo is a very fast compressor (see http://www.oberhumer.com/opensource/lzo/). I've implemented it by using two new compression levels. Compression level 10 is for fast compression using lzo1x-1 algorithm. Compression level 11 is for slow compression using lzo1x-999 algorithm.

[adding libguestfs list, for nbdkit reference below] On 10/4/18 8:39 AM, Stefan Fröberg wrote: > Hello. > Is it possible to improve NBD throughtput with LZO compression ? As in, have a way for the client and server to negotiate that both understand an LZO extension, at which point the client can request a read or write with a flag set to mark that the data is LZO-compressed, for less

On Tue, 15 Oct 2024 14:20:02 +0400 Mariam Arutunian <mariamarutunian at gmail.com> wrote: > Package: libxen > Version: 4.17.3 > Severity: normal > X-Debbugs-Cc: mariamarutunian at gmail.com > > Dear Maintainer, > A vulnerability identified as CVE-2014-4608 was discovered and fixed in LZO decompressor in the Linux kernel with the following commit:

The size of de/compress buffer and LZO1X_MEM_COMPRESS is small enough. Allocating it with kmalloc rather than vmalloc is preferred. This patch depends on my previous patch, “btrfs: fix decompress buffer size”. Signed-off-by: Kyungsik Lee <kyungsik.lee@lge.com> Cc: David Sterba <dsterba@suse.cz> --- fs/btrfs/lzo.c | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-)

Hello, I try to install tinc under cygwin. When I make an ./configure with tinc-1.0.1 I get the error-message checking for lzo1x_1_compress in -llzo... no configure: error:"lzo libraries not found" I have installed lzo-1.08. But it was not from the cygwin-Homepage and so I think that there was a wrong installation-path for the lzo-libraries. How can I find out where to install the

Hi, I planned to boost my btrfs performance today. here some errors I met: my ''btrfs filesystem show'' result: ~ # btrfs filesystem show failed to read /dev/sr0 Label: none uuid: 9b9aa9d9-760e-445c-a0ab-68e102d9f02e Total devices 1 FS bytes used 36.59GB devid 1 size 49.52GB used 49.52GB path /dev/sda6 Label: none uuid: 559dec06-4fd0-47c1-97b8-cc4fa6153fa0

Originated/took from Steffen Winterfeldt and Michael Matz in opensuse's Syslinux package: https://bugzilla.opensuse.org/show_bug.cgi?id=1125616 "fix lzo memory aliasing issue" --- lzo/Makefile +++ lzo/Makefile @@ -19,6 +19,8 @@ LIB = lzo.a BINS = prepcore +OPTFLAGS += -fno-strict-aliasing + all : makeoutputdirs $(BINS) makeoutputdirs: -- -Ady

#!/bin/bash #./configure-fedora-compile-mingw32.sh #./configure --host=i686-pc-mingw32 --with-lzo=./lzo-2.03/ --with-lzo-include=./lzo-2.03/include/ --with-lzo-lib=./lzo-2.03/ #./configure --host=i686-pc-mingw32 --with-lzo=./lzo/ --with-lzo-include=./lzo/include/lzo/ --with-lzo-lib=./lzo/ #./configure --host=i686-pc-mingw32 \ # --with-lzo=$HOME/Dropbox/SOURCE/tinc/lzo-2.03/ \ #

CentOS Errata and Security Advisory 2014:1012 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-1012.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 8cf24ac8ef762128866d8095f54230a8b5e7a32e765faf88a88ed409eda62121 php-5.3.3-27.el6_5.1.i686.rpm

Hi all, as suggested on the mailing list I have converted the updated LZO code into git, so please pull my "lzo-update" branch from git://github.com/markus-oberhumer/linux.git lzo-update You can browse the branch at https://github.com/markus-oberhumer/linux/compare/lzo-update I''d ask some official kernel maintainer for review and to push this into linux-next so that it

CentOS Errata and Security Advisory 2014:0043 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0043.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 6611318ec0b1db26f564df6ee47c9e1bdf88696ddcd943ebeda373154aba5617 bind-9.8.2-0.23.rc1.el6_5.1.i686.rpm

CentOS Errata and Security Advisory 2014:0321 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0321.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: ed63a0745a91e66a8085e76cd8a4724ced643931fcf0a497d8ab96c4e0d9d331 net-snmp-5.5-49.el6_5.1.i686.rpm

I just setup a new SSD with my laptop root filesystem, and at the time I though, "eh, I''ll just use zlib compression during the first copy, and then switch to lzo afterwards to maintain write speed when I''m using the laptop after the copy and reboot". Now, I rebooted with the new ssd and zlib compressed rootfs, and it seemed to boot slower than it did before with the

The prescription for Boot Info Table says that checksumming begins at byte 64 of isolinux.bin. When prepcore writes isolinux.bin it begins copying bytes from the input file at the offset given by variable "start". But it begins checksumming at offset 64 of the input file. The problem exists since introduction of prepcore by release 4.00. ISO 9660 programs usually fix it when they write

CentOS Errata and Security Advisory 2014:0126 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0126.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 07c4f6e0049e9e53255b3effe63421d64d48de4eafc116b28c9b77c63a8e24ec openldap-2.4.23-34.el6_5.1.i686.rpm

- Add incompat flag, otherwise btrfs-progs will report error when operating on btrfs filesystems mounted with lzo option. - Allow to turn on lzo compression for defrag operation: # btrfs filesystem defragment -c[zlib, lzo] <file> Note: "-c zlib" will fail, because that''s how getopt() works for optional arguments. Signed-off-by: Li Zefan