It’s probably a good idea to remove all the old libs needed by older llink versions.

funpkg -r /ffp/var/packages/libdvdcss*
funpkg -r /ffp/var/packages/libdvdnav*
funpkg -r /ffp/var/packages/libdvdread*

The new packages are here:

• llink-2.2.2-1.ffp0.5.tgz
• libdvdcss-1.2.10-1.ffp0.5.tgz

Enjoy!

P.S.  I don’t really use this anymore since the popcorn hour folks increased the SMB performance.  What do you guys use this with?

UPDATE (8/8/2008): Due to a regression with handling .vob files in the VIDEO_TS folder, I have packaged 2.1.1 (build 1000 – current testing version) – try that if you have issues with 2.1.0

(You can read my original review here)

I’ve only done basic testing, but from what I have seen, this llink version rocks!  The UI is much snappier and there is a new theme that looks like the default popcorn hour’s theme!  Nice!  I tested only a couple of .avi and .mkv files which worked great.  I’m not sure if anything else broke…  If anyone has any issues let me know.

Grab these files (the only one that has been updated has been llink, but the others are posted for convenience).

• llink-2.1.0-1.ffp0.5.tgz (new)
  • llink-2.1.1-3.ffp0.5.tgz (build 1000) [optional]
• libdvdcss-1.2.9-1-ffp0.5.tgz
• libdvdread-0.9.7-1-ffp0.5.tgz

NOTE: If you made changes to your llink.conf file, be sure to back them up!  Those changes will need to be merged into the new llink.conf file.

Enjoy!

P.S.  It would be sweet if any of you click on the non-annoying google ad That is, if you’re not already using adblock plus.  And if you aren’t using it, perhaps it’s time to upgrade your browser!

Well, we have a new version of llink!  Read my old review here!  This version can now browse inside of .iso and .img files!  One of the issues I had with the old version!  Sweet!

Download these files:

• llink-2.0.8-1-ffp0.5.tgz
• libdvdcss-1.2.9-1-ffp0.5.tgz
• libdvdread-0.9.7-1-ffp0.5.tgz

Enjoy!  If there are any issues, let me know!

Obviously, you’d need to set up automatic login with ssh to use the scripts below…

my crontab entry looks like:

5 3 * * * /mnt/HD_a2/bin/backup.sh >/mnt/HD_a2/ffp/log/backup.last.log 2>&1

backup.sh – I have several backup scripts called from here – but I am only showing the one for the encrypted remote backup

PATH=/ffp/bin:/ffp/sbin:$PATH
echo "==== Remote Encrypted Backup ===="
/mnt/HD_a2/bin/encBackup.sh
echo "==== Backup Done! ===="

encBackup.sh

#!/bin/bash
# Export some ENV variables so you don't have to type anything

trace () {
stamp=`date +%Y-%m-%d_%H:%M:%S`
echo "$stamp: $*" >> /ffp/log/backup.log
}

export AWS_ACCESS_KEY_ID="YOUR_ACCESS_KEY"
export AWS_SECRET_ACCESS_KEY="YOUR_SECRET_KEY"
export PASSPHRASE=SomeVeryLongAndHardToGuessPassphrase

GPG_KEY=YOUR_GPG_KEY

OLDER_THAN="6M"

# The source of your backup
#SOURCE=/
SOURCE=/mnt/HD_a2/Backups/SecureBackup

# The destination
# Note that the bucket need not exist
# but does need to be unique amongst all
# Amazon S3 users. So, choose wisely.
#DEST="s3+http://YOUR_BUCKET_NAME"
DEST=scp://user@remoteSshServer.com/SecureBackup

FULL=
if [ $(date +%d) -eq 1 ]; then
FULL=full
fi;

trace "Backup for local filesystem started"

trace "... removing old backups"

duplicity remove-older-than ${OLDER_THAN} ${DEST}

trace "... backing up filesystem"

duplicity \
${FULL} \
--tempdir /ffp/tmp \
-v4 \
${SOURCE} ${DEST}

#    --encrypt-key=${GPG_KEY} \
#    --sign-key=${GPG_KEY} \
#    --include=/boot \
#    --include=/etc \
#    --include=/home \
#    --include=/lib \
#    --exclude=/root/.jungledisk/cache \
#    --exclude=/root/.cpan \
#    --include=/root \
#    --include=/usr \
#    --exclude=/var/tmp \
#    --include=/var \
#    --exclude=/** \
#    ${SOURCE} ${DEST} >> ${LOG} 2>&1

trace "Backup for local filesystem complete"
trace "------------------------------------"

# Reset the ENV variables. Don't need them sitting around
export AWS_ACCESS_KEY_ID=
export AWS_SECRET_ACCESS_KEY=
export PASSPHRASE=

encRestore.sh – my restore script

#!/bin/bash
# Export some ENV variables so you don't have to type anything

export AWS_ACCESS_KEY_ID="YOUR_ACCESS_KEY"
export AWS_SECRET_ACCESS_KEY="YOUR_SECRET_KEY"
export PASSPHRASE=PasswordThatWasUsedToEncrypt

GPG_KEY=

# The destination
# Note that the bucket need not exist
# but does need to be unique amongst all
# Amazon S3 users. So, choose wisely.
#DEST="s3+http://YOUR-BUCKET-NAME"
DEST=scp://user@remoteSshServer.com/SecureBackup

if [ $# -lt 3 ]; then echo "Usage $0 <time> <file> <restore-to>"; exit; fi

duplicity \
--tempdir /ffp/tmp \
--file-to-restore $2 \
--restore-time $1 \
${DEST} $3

# Reset the ENV variables. Don't need them sitting around
export AWS_ACCESS_KEY_ID=
export AWS_SECRET_ACCESS_KEY=
export PASSPHRASE=

Wow, llink is great!  It’s quite a bit better then SMB and NFS – at least when using the dns323.  I’ve compiled the version 2.0.6, grab it from the bottom of the post.

Issues with SMB:

• Too damn slow!  I’m not sure if it’s the protocol, the popcorn hour (PCH), or the dns323, but SMB is not usable for streaming HD movies

Issues with NFS:

• Can’t browse directories!  Again, I’m not quite sure where the problem is – most likely the PCH since I am using NFS with my laptop and that works perfectly

Enter llink:
The Good:

• It’s fast!  Fast enough to stream HD content (1080p .mkv)
• Works perfectly with directories… (It’s shocking I need to list this as a positive)
• Automatically discovered by the PCH – just go to ‘Media Sources’ and the dns323 will be listed… nice!

The Bad:

• Currently can’t play .iso files
• Won’t play back the VIDEO_TS folder without having to go and click on each individual video file.

Well, that’s all I have found out for now.  I will experiment more and update if anything changes.

I’ve compiled and uploaded version 2.0.6 and it appears to be working great.  Grab it here!.

Duplicity backs up directories by producing encrypted tar-format volumes and uploading them to a remote or local file server. Because duplicity uses librsync, the incremental archives are space efficient and only record the parts of files that have changed since the last backup. Because duplicity uses GnuPG to encrypt and/or sign these archives, they will be safe from spying and/or modification by the server.

I have been using this since June 1st now and it has been working great!  I had to compile and install several things to get it to work, but in the end, it works perfectly when using ffp0.5.

The packages I used

• duplicity-0.4.12-1.ffp0.5.tgz
• Python-2.5.2-2.tgz
  • Originally from here
• gnupg-1.4.9-1-ffp0.5.tgz
• GnuPGInterface-0.3.2-1.ffp0.5.tgz
• librsync-0.9.7-1-ffp0.5.tgz
• pexpect-2.3-1.ffp0.5.tgz
• boto-1.3a-1.ffp0.5.tgz

I made these packages after I installed everything from source because I wanted to share with everyone.  If they are not perfect, let me know and I will try to fix it.

I now have a ‘SecureBackup’ folder on the dns323 that gets pushed (only the changes) up to my webserver every night via ssh.  Only truly important stuff goes in there.

I have tested to make sure that the version of duplicity that is installed on my Debian Sid box is able to restore all files, and it works great!

Also note, duplicity also works with amazon S3 – which I haven’t tested with, but in theory, that is a GREAT option for anyone who doesn’t already have an offsite backup location.  If there is interest, I could attempt to get boto posted as well (needed for S3).

UPDATE: You can see the shell scripts used here.

UPDATE: Boto package has been included

UPDATE: Upgraded to duplicity 0.4.12.  Seems to work for me