similar to: lzo compression support for tinc

Source: xen Version: 4.2.1-2 Severity: serious Tags: jessie sid User: debian-qa at lists.debian.org Usertags: qa-ftbfs-20130609 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[2]: Entering directory `/?PKGBUILDDIR?' > mkdir -p debian/build/build-utils_amd64 > cp -al CODING_STYLE COPYING

I got the file that was sent to me the other day. Unfortunitly it did not solve my problems. After a lot of hacking I have been able to get release 1.0 to almost compile. I have finally gotten all of the dependancies worked out under OpenBSD 3.2. This next error has me stumped. I can tell that it is looking for a file but have no idea how to create the file. This is the output of the the

On 25/11/14 22:05, Andy Ritger wrote: > On Tue, Nov 25, 2014 at 10:57:44AM -0500, Ilia Mirkin wrote: >> On Mon, Nov 24, 2014 at 8:33 PM, Andy Ritger <aritger at nvidia.com> wrote: >>> On Fri, Nov 21, 2014 at 01:39:55AM -0500, Ilia Mirkin wrote: >>>> On Fri, Nov 21, 2014 at 1:16 AM, Andy Ritger <aritger at nvidia.com> wrote: >>>>> Hi Ilia,

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(-)

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

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

CentOS Errata and Security Advisory 2014:0861 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0861.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 5573a762c075a0d03f070c6bd0b47c41311fff66e21e034863d514ee65d8c081 lzo-2.03-3.1.el6_5.1.i686.rpm

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

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

[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

Hi Some developers here said a long time ago that someone should show the code for LZO compression support for ZFS before talking about the next step. I made that code with a friend and we also made a little benchmark to give a first impression: http://denisy.dyndns.org/lzo_vs_lzjb/ I hope we made no technical error, but if you find something not accurate, we will correct it. Denis -- This

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

I''ve noticed that: - with x86-64 Fedora 15 DVD install images: - du -sh <ROOT VOLUME> was 36 GB - btrfs df | grep -i data have shown over 40 GB used - without - du -sh <ROOT VOLUME> is 34 GB - btrfs df | grep -i data have shown less then 34 GB used It seems that iso files are considered compressable while they may not be (and penalty is severe - 3x). Regards

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

- 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

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

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

I have recently set to * to play with and I'm getting the hang of it.. I've seen various posts about problems where the SIP clients are behind NAT but I anted to ask a slightly different question. At the current CVS can the * SIP client register with a SIP provider (such as ICH) when the * box itself is behind a NAT. I have an ICH account which I can configure fine on an ATA 186 using

Please see the attached file and let me know if you need any more information. /Sam Sam Sexton <mailto:sam.sexton@reuters.com> Reuters Coventry Automated Dealing Technologies Phone: +44 24 7625 6562 Fax: +44 24 7655 5203 --------------------------------------------------------------- - Visit our Internet site at http://www.reuters.com Get closer to the

I miss the stars when doing scp. My suggestion for progressmeter.c makes scp to display different fields on different terminal widths. Maybe this is useful for you. Once in "start_progress_meter()" the outlook of the progressline is calculated. In "draw_progress_meter()" sprintf() instead of snprintf() together with some strlen()'s can be used, because the buffersize has