public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: rsync 3.2.0
Date: Thu, 25 Jun 2020 09:54:41 +0100	[thread overview]
Message-ID: <CD641D70-4AA4-4AE0-8168-EAB88198F831@ipfire.org> (raw)
In-Reply-To: <8ed12d36-925a-7dbb-7ed6-9d37ea5dfa81@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1954 bytes --]

Hi,

> On 20 Jun 2020, at 16:09, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> Hi,
> 
> rsync 3.2.0 is out and I just had time...for details see:
> https://download.samba.org/pub/rsync/src/rsync-3.2.0-NEWS
> 
> Right now running under Core 145 / x86_64. No problems.
> 
> But I still have two questions.
> 
> In order to use the new xxhash checksum support and zstd compression,
> the corresponding kernel modules would need to be activated. Do we want
> or need these?

You won’t need kernel modules for this. You simply need the relevant libraries.

I have packaged those for IPFire 3 and they are easy to build and have no further dependencies. So I would recommend to at least add zstd.

https://git.ipfire.org/?p=ipfire-3.x.git;a=blob;f=rsync/rsync.nm;h=528dcfc0a377bc770a45a8f88af00079eb26dc93;hb=b40cdb8c182d8b4aa05c6e23cc67118c4aa4853c
https://git.ipfire.org/?p=ipfire-3.x.git;a=blob;f=zstd/zstd.nm;h=e5afd342b9ad2ae0c0f394116ef2dfddea670413;hb=8bcac5c8cda49b91fe68bef64c3ad975b80a43ca

> 
> For now, I disabled both with these configure options:
> 
> ...
> 	--disable-xxhash \
> 	--disable-zstd
> ...
> 
> Do we want (would someone use) the new 'rsync-ssl'-script? On a firewall!?

I tried to find out what this is useful for. It doesn’t harm us and calls openssl. So I would just leave it in there.

> Current capabilities:
> 
> ***SNIP***
> root(a)ipfire: /tmp # ./rsync --version
> rsync  version 3.2.0  protocol version 31
> Copyright (C) 1996-2020 by Andrew Tridgell, Wayne Davison, and others.
> Web site: http://rsync.samba.org/
> Capabilities:
>    64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints,
>    socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append,
>    ACLs, xattrs, iconv, symtimes, prealloc, SIMD
> Checksum list:
>    md5 md4 none
> Compress list:
>    lz4 zlibx zlib none
> ***SNAP***
> 
> Best,
> Matthias

-Michael

  reply	other threads:[~2020-06-25  8:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-20 15:09 Matthias Fischer
2020-06-25  8:54 ` Michael Tremer [this message]
2020-06-25 15:28   ` Matthias Fischer
2020-06-25 15:35     ` Michael Tremer
2020-06-25 15:56       ` Matthias Fischer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CD641D70-4AA4-4AE0-8168-EAB88198F831@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox