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?
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!?
Current capabilities:
***SNIP*** root@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
Hi,
On 20 Jun 2020, at 16:09, Matthias Fischer matthias.fischer@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=528dcfc0a... https://git.ipfire.org/?p=ipfire-3.x.git;a=blob;f=zstd/zstd.nm;h=e5afd342b9a...
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@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
Hi,
On 25.06.2020 10:54, Michael Tremer wrote:
Hi,
On 20 Jun 2020, at 16:09, Matthias Fischer matthias.fischer@ipfire.org wrote:
Hi,
rsync 3.2.0 is out and I just had time...
In fact, I'm at 3.2.1. See below.
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.
Ok. I wasn't sure. I found some 'zstd's in the rootfiles and thought we would need these.
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.
I am at it.
https://git.ipfire.org/?p=ipfire-3.x.git;a=blob;f=rsync/rsync.nm;h=528dcfc0a... https://git.ipfire.org/?p=ipfire-3.x.git;a=blob;f=zstd/zstd.nm;h=e5afd342b9a...
Thats exactly what I needed - thanks - I'll take a look.
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.
Ok.
Please note:
'rsync 3.2.1' just came out. I'm testing - and working on 'zstd 1.4.5' (weekend, I think).
If you want, we could skip 3.2.0 => no need to merge this patch.
I could mark 3.2.0 as 'superseded' in patchwork and we'll go straight to 3.2.1.
Opinions?
Best, Matthias
Hi,
On 25 Jun 2020, at 16:28, Matthias Fischer matthias.fischer@ipfire.org wrote:
Hi,
On 25.06.2020 10:54, Michael Tremer wrote:
Hi,
On 20 Jun 2020, at 16:09, Matthias Fischer matthias.fischer@ipfire.org wrote:
Hi,
rsync 3.2.0 is out and I just had time...
In fact, I'm at 3.2.1. See below.
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.
Ok. I wasn't sure. I found some 'zstd's in the rootfiles and thought we would need these.
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.
I am at it.
https://git.ipfire.org/?p=ipfire-3.x.git;a=blob;f=rsync/rsync.nm;h=528dcfc0a... https://git.ipfire.org/?p=ipfire-3.x.git;a=blob;f=zstd/zstd.nm;h=e5afd342b9a...
Thats exactly what I needed - thanks - I'll take a look.
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.
Ok.
Please note:
'rsync 3.2.1' just came out. I'm testing - and working on 'zstd 1.4.5' (weekend, I think).
If you want, we could skip 3.2.0 => no need to merge this patch.
I could mark 3.2.0 as 'superseded' in patchwork and we'll go straight to 3.2.1.
Yes, absolutely do that. There is no point in merging 3.2.0 if 3.2.1 is already under works.
Best, -Michael
Opinions?
Best, Matthias
Hi,
On 25.06.2020 17:35, Michael Tremer wrote:
...
Please note:
'rsync 3.2.1' just came out. I'm testing - and working on 'zstd 1.4.5' (weekend, I think).
If you want, we could skip 3.2.0 => no need to merge this patch.
I could mark 3.2.0 as 'superseded' in patchwork and we'll go straight to 3.2.1.
Yes, absolutely do that. There is no point in merging 3.2.0 if 3.2.1 is already under works.
Ok. Done.
Besides, I took a look. ;-)
Right now on my ToDo-list (compiling):
rsync 3.2.1 (Is it ok if I take over the build options of IPFire 3.0!?)
popt 1.18 (With 1.16, we're more than 9 years behind...)
And - "because it stood in my way": ntp 4.2.8p15
And last but not least: zstd 1.4.5
Best, Matthias
-
Matthias Fischer -
Michael Tremer