similar to: xdelta files for security patches

Hello, lately I've been playing with the idea of doing in-place updates of systems using either rsync or xdelta. However, both rsync and xdelta seem to be dead set on writing a new file first, and then atomically exchanging it with the old file. Now, as I want to apply a binary delta to a full filesystem, bigger than the available temporary space, this really makes rsync and xdelta

Hi I have a system that I'm trying to run `yum update` on. It fails with the following error: Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Check Error: file /usr/share/man/man1/xdelta.1.gz from install of xdelta-1.1.4-1.el5.rf conflicts with file from package xdelta-1.1.3-20 file /usr/share/emacs/site-lisp/psvn.el from install of

xdelta results: 666198016 CentOS-4.0-Beta-Binary-CD1.iso 635330560 CentOS-4.0-Beta-Binary-CD2.iso 661059584 CentOS-4.0-Beta-Binary-CD3.iso 662018048 CentOS-4.0-Beta-Binary-CD4.iso 444139520 CentOS-4.0-Beta-Binary-CD5.iso - 658491392 CentOS-4.0.rc1-i386-bin1of5.iso 611952640 CentOS-4.0.rc1-i386-bin2of5.iso 666099712 CentOS-4.0.rc1-i386-bin3of5.iso 663128064 CentOS-4.0.rc1-i386-bin4of5.iso

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-05:01.telnet Security Advisory The FreeBSD Project Topic: telnet client buffer overflows Category: contrib Module: contrib/telnet Announced:

I'm interested in these very questions (librsync-rsync relationship, remaining limitations of rsync, active prospects for ground-up rewrites), Google searches for rsync info have proved a little too vague due to the programs ubiquity. Much has certainly changed since this was written, could some people with knowledge in these areas could update martin's response for the state of rsync,

Hi, Where can I get good pointers on the rolling checksum algorithm used in rsync? I need an 8-bit or 12-bit rolling checksum too. Any place where "rolling" checksum algorithms are discussed? Seun Osewa ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/

Hi list, is there any working solution for deduplication of data for centos? We are trying to find a solution for our backup server which runs a bash script invoking xdelta(3). But having this functionality in fs is much more friendly... We have looked into lessfs, sdfs and ddar. Are these filesystems ready to use (on centos)? ddar is sthg different, I know. Thx Rainer

Hi, I wanted to get some opinions on this subject before I submit a PR about it. I don't know if there are any pitfalls with the 'fix' I suggested and though it best to run it past people here before submitting. If there's a better place to post this please let me know (freebsd-ports?). The send-pr output I was about to send explains everything so I'll just paste it here:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-07:03.ipv6 Security Advisory The FreeBSD Project Topic: IPv6 Routing Header 0 is dangerous Category: core Module: ipv6 Announced:

Hi All, I'm running CentOS 5.3 x86, and recently my yum update isn't running as it should. It pops up with sub conflict messages for i386 packages, which I don't need - even though yum is downloading them. Due to this sub conflict messages, I'm not able to update/install my x86 packages, as the installation stops at the error message. Anybody, any idea how to come over

On the advisory about the realpath problem it says that it was corrected: RELENG_4_8 src/UPDATING 1.73.2.80.2.3 src/lib/libc/stdlib/realpath.c 1.9.14.1 src/sys/conf/newvers.sh 1.44.2.29.2.2 I ran cvsup and when I look at my src/lib/libc/stdlib/realpath.c I see

Full_Name: Naoki Takebayashi Version: 0.65.0+R-release.diff (Oct 6, 1999) OS: Linux/Alpha Submission from: (NULL) (129.79.224.171) This will fix the "problem 2 (crash in fft)" in Bug ID #277 On Linux/Alpha, make check failed because R could not handle the following example in base-Ex.R ##___ Examples ___: # The Old Faithful geyser data data(faithful) : : ## Missing values: x <-

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-03:08.realpath Security Advisory The FreeBSD Project Topic: Single byte buffer overflow in realpath(3) Category: core Module: libc Announced:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-06:25.kmem Security Advisory The FreeBSD Project Topic: Kernel memory disclosure in firewire(4) Category: core Module: sys_dev Announced:

With the help of Jan Iven I have been able to compile openssh-2.9.9p2 on Solaris 2.6 with AFS/kerb4 support using gcc. ./configure --sysconfdir=/etc/ssh --with-tcp-wrappers \ --with-egd-pool=/var/run/egd-pool \ --with-kerberos4=/usr/athena --with-afs=/usr/afsws to do this I modified the resulting Makefile, from: CPPFLAGS=-I. -I$(srcdir) -I/usr/local/ssl/include

Hi there, System is FreeBSD 4.9 Stable Had a problem during a portupgrade that when portupgrade did some cleaning a directory could not be deleted because it were not empty. However, it was empty. rm -rf didn't help either. Because I didn't know what to do I decided to boot. At system startup fsck was started which produced the message: unexpected softupdate inconsistency and also that

Hello, I''d like to know if there has been any discussion about adding a new feature to write (add) data at an offset, but without overwriting existing data, or re-writing the existing data. Essentially, in-place addition/removal of data to a file at a place other than the end of the file. Some possible use-cases of such a feature would be: (a) Databases (currently hack around this by

We're being ping-flooded by the Nachi worm, which probes subnets for systems to attack by sending 92-byte ping packets. Unfortunately, IPFW doesn't seem to have the ability to filter packets by length. Assuming that I stick with IPFW, what's the best way to stem the tide? --Brett Glass

At the end of March, the RELENG_4_8 (sometimes called 4.8-SECURITY) branch will reach its designated End of Life and cease to be supported by the FreeBSD Security Team. Released in April 2003, FreeBSD 4.8 was the first release designated for "extended" two-year security support instead of the normal one-year support. Over this time, 27 security advisories have been issued which have

CVSup is slow, insecure, and a memory hog. However, until now it's been the only option for keeping an up-to-date ports tree, and (thanks to all of the recent work on vuxml and portaudit) it has become quite obvious that keeping an up-to-date ports tree is very important. To provide a secure, lightweight, and fast alternative to CVSup, I've written portsnap. As the name suggests, this