Suppose I had Windows at home (which sadly I do, it came with the EeeBox I bought). I think the list would look something like this:

• Windows XP (version: yyyy, key: xxxx)
• Trojan-Dropper.Win32.Agent.albv
• Mimail
• ...

Or I'm I going about it the wrong way?

Needless to say, this is fixed in the latest git version.

I now want to convert my shell test suite kludge to something people can run a their computer, so that they can send me the output of a make test.

• WinFS
• Avalon, trimmed down to Aero?

Soon (maybe after a year) they started with the development of Windows 7. Now I read on slashdot that a RC1 release is scheduled RSN.

So developing a entire new OS from scratch(?) takes about 4 years in Redmond and now they want you to believe Windows 7 is a completely new OS and will be better than Vista -- even though development took only a year?

If you believe everything Microsoft says you can always use the following quote, which I have been hearing from people use Microsoft software (even in the DOS era) for years now.

Yes, I know this version sucks, but the next version that comes out will be much better!

rdup -c /dev/null ~/bin | ./rdup-up -t /vol/backup

fails with the following error:

rdup-up: First character should '-' or '+', `01BLOCK00000' at line: 8

This was reported to me by Jared Henley. It is fixed with this commit

You can work around it with, by putting rdup-tr in the pipeline, like so:

rdup /dev/null ~/bin | rdup-tr | ./rdup-up -t /vol/backup

Note: rdup is called without the -c flag!

I wanted to release a new version of rdup anyhow, so expect a 0.9.1 release soonish.

These fixes have just (5 minutes ago) been committed to subversion. So if you check out the latest trunk it should compile on Solaris.

To make it compile I had to uncomment some GNU_GETTEXT_ macros in configure.ac, but I not really using them anyway.

There was also some nagging about major() and minor() which turned out to be a missing #include <sys/sysmacros.h>.

The following bugs were reported (and fixed) in rdup. Thanks to Tom Hendrikx for reporting and fixing some of the issues mentioned here.

incremental backups of symlinks

Incremental backup of symlink and hardlink were b0rked, this is now fixed (revision r1780 and r1781) but this required a change to the internal filelist which is used by rdup.

rdup-simple with one argument

rdup-simple would just go ahead even if you only give it one argument. This is fixed in revision r1775.

rdup-simple -f without any previous backup

This would fail, because the leading directories are not created by rdup-up. This is fixed in revision r1777 by including a mkpath() function and extending the -t flag of rdup-up a little.

rdup-simple output to stderr

Now only the errors are printed to stderr, the rest if echoed to stdout. See revision r1778

.nobackup are not respected

Normally if a .nobackup file is found in a directory the directory is excluded from the backup.

This is fixed in revision r1779.

Due to the internal file format change, the next version of rdup will be 0.7.0 and we are closely going to a 1.0.0 release.