similar to: Rsync 3.1.3pre1 released

On January 15, 2018 1:53 AM, Wayne Davison write: >I have made rsync 3.1.3pre1 available for testing. This release has a couple security fixes, a few new features, and a smattering of bug fixes. >Please test this new release and send email to the rsync mailing list with any questions, comments, or bug reports. Incompatibility introduced at 3.1.3pre1. These are not present at master, which

https://bugzilla.samba.org/show_bug.cgi?id=13224 Bug ID: 13224 Summary: New file handling causes compile issues for NonStop port. Product: rsync Version: 3.1.3 Hardware: Other OS: Other Status: NEW Severity: normal Priority: P5 Component: core Assignee:

I need to reliably boot a server from a USB device. Since USB device ordering can be unpredictable, I wrote a simple early-userspace "init" program to find the root FS on the correct USB device & partition. I have "labeled" the root ext2 FS on the USB drive, and the program searches for the label by examining the bytes at a specific offset from the beginning of the

https://bugzilla.samba.org/show_bug.cgi?id=8265 Summary: Long paths, hardlinks, 'special' files [was: Regression: sockets for 3.0.9pre1] Product: rsync Version: 3.0.9 Platform: All OS/Version: All Status: NEW Severity: blocker Priority: P1 Component: core AssignedTo:

On Mon, Jan 15, 2018 at 6:20 AM, Randall S. Becker <rsbecker at nexbridge.com> wrote: > Incompatibility introduced at 3.1.3pre1. These are not present at master, > which compiles cleanly. > The master branch and 3.1.3pre1 were pretty much the same until just a moment ago (except that the tar files get some generated files that aren't present in git, such as the autoconf

Yet another one of those "it would make sense it" posts. Currently, create_dev in do_mounts.c simply unlinks the device and recreates it. This doesn't seem right. If /dev/hda3 has already been created, by some early-userspace app (udev), there's no need to unlink or even parse the name again. Now, when talking about simple block devices, this doesn't make much of a

Skipped content of type multipart/alternative-------------- next part -------------- diff -urN rsync-3.0.2-orig/generator.c rsync-3.0.2/generator.c --- rsync-3.0.2-orig/generator.c 2008-03-28 10:30:11.000000000 -0700 +++ rsync-3.0.2/generator.c 2008-05-07 15:35:08.317364774 -0700 @@ -1508,6 +1508,7 @@ if (preserve_links && S_ISLNK(file->mode)) { #ifdef SUPPORT_LINKS + int iflags =

OK. Didn't see anything about this in the archives, other than an old post from 2000 about a similar problem, so here goes. Feel free to contact me if I can provide anything else useful. Problem: -------- Major numbers on 64bit Solaris are being dropped, and created as 0 on recieving end. 32bit version works perfectly. Environment: ------------ Solaris 8 or Solaris 9 (haven't tried

I tried rsync 2.6.1cvs on my FreeBSD 4.X boxes. It dumps core when preserve_hard_links and backup. And SUPPORT_HARD_LINKS is true. rsync -avH --delete --backup --backup-dir=/some/backup/dir \ srchost::dir/ dir/ The core says... ------------------------------------------------------------------------ Program terminated with signal 11, Segmentation fault. #0 0x80536c0 in keep_backup

Hi Rich, I ran coverity against febootstrap's head and it spotted four leaks. This fixes them. The first patch plugs three. The second attempts to make the add_link function do what I'm guessing it was intended to do. As is, it was a no-op. >From 7c2ff55613598a1295e213cef36600ad61da7ed6 Mon Sep 17 00:00:00 2001 From: Jim Meyering <meyering at redhat.com> Date: Tue, 10 Jan 2012

Rather complex patch to solve a small user error. Warn if the user is doing something like: virt-builder -o /dev/sdX1 Rich.

The attached patch adds an option --drop-suid which caused rsync to drop setuid/setgid permissions from the destination files. ie, even if the source file is setuid, the target file will not be. Added as we want to rsync the same files to machines both inside and outside our firewalls. For machines inside the firewall some files should be suid, for machines outside the firewalls they should

Fix for: https://bugzilla.redhat.com/show_bug.cgi?id=1354507 Main explanation is in patch #3. Rich.

https://bugzilla.samba.org/show_bug.cgi?id=3806 Summary: makedev has 3 arguments in qnx Product: rsync Version: 2.6.8 Platform: Other OS/Version: Other Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: cooke@sun.ac.za QAContact:

hello hpa, nothing particular stands out, just syncing with latest Debian upload and subsequent patch emails. please review merge or nack. thanks :) maks git pull git://git.debian.org/~maks/klibc.git maks for the changes: Aaron Griffin (1): [klibc] kinit: skip md assembly if mdX exists Colin Watson (1): [klibc] mount/umount FUSE support Harald Jenny (1): [klibc] fstype:

https://bugzilla.samba.org/show_bug.cgi?id=6280 Summary: (Bug incl. PATCH) Linux mknod does not work when syncing fifos and sockets from Solaris Product: rsync Version: 3.0.6 Platform: x64 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:

Hi all, This patch set adds batched discard support to ocfs2. Please check. Thanks. Regards, Tao

https://bugzilla.samba.org/show_bug.cgi?id=2357 ------- Additional Comments From happyspaceinvader@btopenworld.com 2005-02-17 11:09 ------- What I meant to ask was, can this be automatically determined somehow so other users of Windows Services for Unix don't have to hack flist.c like I did? -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are

The difference between kdev_t and dev_t in 2.4 is rather theoretical, no need to clutter up the source for it. Index: src/inode.c =================================================================== --- src/inode.c (revision 969) +++ src/inode.c (working copy) @@ -1877,11 +1872,8 @@ case OCFS_ATTRIB_FIFO: case OCFS_ATTRIB_SOCKET: { -#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,0)

https://bugzilla.samba.org/show_bug.cgi?id=7625 Summary: "Don't know how to make ./*.c" Product: rsync Version: 3.0.7 Platform: s390 OS/Version: Other Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: sebastian.hoffman at