similar to: rsync doesn't checksum for local transfers?

> You are missing the point of the checksum. It is a verification that > the file was assembled on the target system correctly. The only > post-transfer checksum that would make any sense locally would be to > make sure that the disk stored the file correctly which would require > a flushing of the cache and a re-reading of the file. Rsync has no > capability to do this

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 You are missing the point of the checksum. It is a verification that the file was assembled on the target system correctly. The only post-transfer checksum that would make any sense locally would be to make sure that the disk stored the file correctly which would require a flushing of the cache and a re-reading of the file. Rsync has no capability

On Fri, Dec 5, 2014 at 4:30 AM, <devzero at web.de> wrote: > After being written to disk, for both local and remote transfers, the > destination file as a whole is not being re-read for checksumming. > Checksumming is only being done for the reconstruction process: > The checksum is calculated across the bits being received and the > bits being read from the target file, so

On Sunday, January 26, 2020 3:58:31 PM CET Pete Biggs wrote: > > what does Centos 7 do with UPD packets having invalid checksums? > > By default I assume they are just dropped - that's what should happen. Hm that's what thought. > > Are such packets inevitably dropped? > > Applications can specifically disable checksum checking for the kernel > network stack

Hi, what does Centos 7 do with UPD packets having invalid checksums? Are such packets inevitably dropped? Does a network card drop them when it does checksum verification in hardware even before the packets go anywhere? In general, if someone were to send me UPD packets with invalid checksums over the internet, how far would such packets get? In particular, how likely it is that SRTP

rsync in daemon mode is very powerful, yet it comes with one big disadvantage: data is sent in plain. The workarounds are not really satisfying: - use VPN - one needs to set up an extra service, not always possible - use stunnel - as above - use SSH - is not as powerful as in daemon mode (i.e. read only access, chroot, easy way of adding/modifying users and modules etc.) Why was encrypted

Have a directory with a bunch rpms in it, mostly x86_64. Have another directory with a bunch, mostly 'noarch'. Some of the noarch files are already in the x86_64 dir and don't want to overwrite them. They are on the same physical disk, so really, just want the new 'noarch' files hardlinked into the destination. sitting in the noarch dir, I tried: rsync -auv

Please be patient with my ignorance if what I am asking is meaningless in any way. I am not too technically knowledgeable about filesystem internals but I am willing to learn. (I thought of posting to linux-ext4 but did not want to intrude within the technical threads with my layman thread.) From Wikipedia > ReiserFS article > Design section: [quote]ext2 and other Berkeley FFS-like

All, This is a fresh, un-f#$ked-with OpenSUSE install after adding the Tumbleweed repository and doing a dup. I installed the Hypervisor with Tools for which it prompted me for Xen or QEMU and I chose Xen. No bridge was made. When I go to create a fully virtualised machine, it nao has the error: Error: Device 0 (vif) could not be connected. Could not find the bridge, and none was specified.

Fix supermins rpm/zypper detection on openSUSE Tumbleweed Newer version of openSUSE does not use /etc/SuSE-release anymore. Search for the new /etc/SUSE-brand in addition. --- diff --git a/src/rpm.ml b/src/rpm.ml index a5dc67a..400efbd 100644 --- a/src/rpm.ml +++ b/src/rpm.ml @@ -39,7 +39,10 @@ let fedora_detect () =  let opensuse_detect () =    Config.rpm <> "no" &&

from a security perspective this is bad. think of a backup provider who wants to make rsyncd modules available to the end users so they can push backups to the server. do you think that such server is secure if all users are allowed to open up an ssh shell to secure their rsync transfer ? ok, you can restrict the ssh connection, but you open up a hole and you need to think twice to make it secure

> Felix Miata wrote in https://lists.freedesktop.org/archives/nouveau/2020-February/035583.html: OS Kernel State /boot/vmlinuz timestamp >> openSUSE 15.1/kernel 4.12.14 OK 2019-12-06 Fedora 31/5.3.16 kernel OK 2019-12-13 openSUSE 15.2/5.3.16 kernel OK 2019-12-31 Tumbleweed/5.4.7 kernel OK 2020-01-08 Mageia 7/5.4.10 kernel OK 2020-01-09 Mageia 8/5.4.11 kernel OK 2020-01-13

Dear Samba experts, IO would like to ask for help with diagnose why my Samba version 4.7.0-git. 23.4e3f0fb9d15SUSE-oS13.3-x86_64 in openSUSE Tumbleweed can not authentificate me on Windows server 2003 domain in /etc/fstab I have working combination - smb version only vorks if set to 1.0 //192.168.1.131/shares /home/fodrek/shares cifs credentials=/home/fodrek/

Video and input drivers Subgroups and projects on gitlab does not list modesetting DDX, presumably because it's not packaged separately from the server. Where's the right place to report a modesetting DDX bug that manifests only on an NVidia GPU? Directly against the server https://gitlab.freedesktop.org/xorg/xserver? Here are some particulars: How can I tell whether this should be

On Sunday, January 26, 2020 11:18:36 PM CET Pete Biggs wrote: > First of all - disclaimer - I'm no network specialist, I just read and > am interested in it. I may get things wrong!! > > > Both physical interfaces show the same. But does this mean it's on as in > > "rx- checksumming: on" or off as in "tx-checksum-ipv4: off [fixed]"? > > As

HI! After the last OS update (openSUSE Tumbleweed) with libvirt being updated from 3.0.0 to 3.1.0 starting the VMs (qemu-kvm) does not work anymore: error: internal error: child reported: Kernel does not provide mount namespace: Permission denied Kernel was updated before to 4.10.1 and worked just fine with libvirt 3.0.0 packages. Any clue how to work around that? Ciao, Michael.

Hi! The same Inar reported for rawhide (https://stat.ethz.ch/pipermail/r-devel/2023-March/082482.html) is true for SuSE's distros. Right now R does not compile with libcurl8, but SuSE Tumbleweed/Factory switched to 8 a week ago. Would be great, if the patch Inar provided could be applied to main. Detlef -- "Wozu leben wir, wenn nicht dazu, uns gegenseitig das Leben einfacher zu

Hi, we have a own C++ code running usually on Linux and OS X. The code is known to run on Windows compiled natively. It is a text-based academic code (Finite-Element) using some Fortran Libs compiled with the cross-compiler and Intels MKL. Now I cross-compile the code using mingw 6.2.0 from openSUSE. We have a testsuite for our code with 150 complete test runs (the whole application runs

I recently replaced a 8600 GT with the above card on openSUSE Tumbleweed x86_64. The screen now flickers and when I change desktops it takes a some 10 to 15 seconds to display the new windows. e.g if I change from desktop 1 (konsole) to desktop 8 (thunderbird) it switches but konsole is displayed for 10 to 15 seconds before thunderbird appears. Occasionally the screen flickers wildly before

Hi, Anybody knows when the new kernel package will be ready? regards,