RDUP-TR(1)

📦
version 1.1.15 · 2 versions
, in nixos 26.05, ubuntu jammy, ubuntu noble

💖 RDUP-TR(1) — the rdup manual, but make it cute 💖

okay bestie, gather round 🫶 this is rdup-tr, straight out of the rdup manual (section 1, the user commands, iykyk). It's the lil transformation station of the rdup universe and honestly? She's giving glow-up ✨

🌸 NAME 🌸

rdup-tr — transform rdup output 💅

✨ SYNOPSIS ✨

rdup-tr [OPTION]...

that's it. that's the whole vibe. no positional args, no drama, just options 🎀

🦋 DESCRIPTION 🦋

So here's the tea ☕ — rdup-tr takes rdup output and turns it into something else. And "something else" can be a tar, a cpio, a pax archive, or another rdup stream. Versatile queen 👑

💡 The rdup archive must be handed to rdup-tr's standard input. No stdin, no service.

You can select multiple types of output (that's the -O flag, babe), but lowkey you need to be aware that you may lose some information in formats other than rdup's own. There's a whole table for it, keep reading 📖

You may also feed rdup-tr nothing but a list of pathnames — that's what the -L flag is for 🍓

Here's what happens to your output depending on what you feed in. The legend first:

  • 0 — OK, we ate, no notes 😌
  • D — delete information is lost 😭
  • H — hardlink information is lost 😭

Now the actual combos:

  • input rdup → output tar,cpio,pax: D (delete info, gone girl 💀)
  • input rdup → output rdup: 0 (perfect, iconic, no loss 🌟)
  • input filelist → output tar,cpio,pax: DH (both delete and hardlink info lost, we're sobbing 🥲)
  • input filelist → output rdup: H (just the hardlink info lost)

🎀 OPTIONS 🎀

  • -L — Select list input format. Normally rdup-tr accepts rdup output, but with this option you can hand it a list of path names instead. > ⚠️ Heads up bestie: with list input, rdup-tr will stat() each file, so this can not be used in remote back ups. Periodt.
  • -O — Output format. Can be 'tar', 'cpio', 'pax' or 'rdup'. It defaults to 'rdup'. Pick your fighter 💫
  • -X _key_ — Read the encryption key from the file _key_ and encrypt all paths with Blowfish and this key and iv. After the encryption the binary data is converted into ASCII using an URL safe (Section 4 of RFC 3548) version of base64 encode. 🔐
🚨 The encryption key must be on the first line, and the key size must be 16 and 8 bytes for the iv — so 24 in total. Don't play with this, fr fr.
  • -Y _key_ — Read the decryption key from the file _key_ and decrypt all paths with Blowfish and this key. Before the encryption the paths are converted to binary by using an URL safe version of base64 decode. 🔓
  • -c — Force output to the tty. Normally rdup-tr wants to see its output redirected. She's shy 🙈
  • -v — Be more verbose. Prints the processed file names to standard error. Chatty era 🗣️
  • -V — Print rdup-tr's version.
  • -h — A short help. Your lil rescue button 🆘

🌈 EXAMPLES 🌈

The following is possible 👇

rdup -P gzip -P "mcrypt -f KEY -c" /dev/null /home | \
rdup-tr -O tar -X<(echo secret) | gzip > \
my-home-zipped-crypted-pathcrypted-tar.gz

That is: all files under /home are gzipped and encrypted on a per file basis (first line). Further more, all pathnames are Blowfish encrypted (second line) with the key 'secret'. This is put in a tar file, which is then compressed, resulting in the final output (final line). A whole pipeline, a whole journey 🚀

Creating a compressed and encrypted tar archive out of a full rdup dump might be done as follows:

rdup -P gzip -P "mcrypt -f KEY -c" /dev/null /home | \
rdup-tr -O tar > my-home-zipped-and-crypted.tar

Or even pack and unpack it on the fly 🛫

rdup -P gzip -P "mcrypt -fKEY -c" /dev/null /home | rdup-tr -Otar | \
ssh user@remotehost tar xvCf /tmp -

Or encryption with openssl 🔐

rdup -P "openssl enc -e -des-cbc -k secret" /dev/null /home

Or, compressing with gzip, encrypting with openssl and then compressing the entire archive yet again (double compression, main character energy 👑)

rdup -P gzip -P "openssl enc -e -des-cbc -k secret" /dev/null /home | \
gzip > my_compressed_encrypted_rdup_archive.gz

💀 EXIT CODE 💀

rdup-tr returns a zero exit code on success, otherwise 1 is returned. No in-between, no situationship.

🫶 AUTHOR 🫶

Written by Miek Gieben. A legend, honestly.

🐛 REPORTING BUGS 🐛

Report bugs to <miek@miek.nl>. Tell him everything, he can handle it 💌

⭐ SEE ALSO ⭐

http:/www.miek.nl/projects/rdup/ is the main site of rdup. Also see rdup(1), rdup-up(1) and rdup-backups(7). Go read the whole family, they're all icons 🧚

Copyright (C) 2005-2010 Miek Gieben. This is free software. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Like, none. Zero. Nada. 🚫

Licensed under the GPL version 3. See the file LICENSE in the source distribution of rdup.

and that's the whole page, bestie!! 🎀 this was rdup-tr from the rdup manual, version 1.1.14, dated 27 Nov 2008 — yeah she's vintage, and vintage is iconic 💅✨ no cap. now go pipe something into her stdin and slay 🦋🌸

📦 where this page comes from