# rsync Published articles for rsync. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Libreboot 2025 Release Schedule Revised DevFeed: [Libreboot 2025 Release Schedule Revised]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: release Language: en Sources: [News about Libreboot releases and development]() Topics: [libreboot](), [releases](), [Git](), [rsync]() Tags: [2025](), [bios](), [canoeboot](), [coreboot](), [free-software](), [git](), [libre](), [libreboot](), [opensource](), [release](), [release-schedule](), [rsync](), [uefi]() ### AI overview Libreboot revises its 2025 release schedule: stable releases are planned for June and December, while releases between them may be revisions to the current stable release or release candidates for the next stable release. Release candidates will be removed when superseded. ### Source excerpt Article: NEW Libreboot 2025 release schedule Web link: https://libreboot.org/news/revisions.html ## ThinkPad X201 support removed from Libreboot DevFeed: [ThinkPad X201 support removed from Libreboot]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: news Language: en Sources: [News about Libreboot releases and development]() Topics: [libreboot](), [coreboot](), [rsync]() Tags: [article](), [bios](), [canoeboot](), [coreboot](), [free-software](), [issue](), [libre](), [libreboot](), [news](), [opensource](), [rsync](), [safety](), [thinkpad](), [uefi]() ### AI overview Libreboot removed support for the ThinkPad X201 and other older Arrandale machines after discovering that fan controls fail when using a neutered Intel ME image. Coreboot remains possible with the full Intel ME image, but Libreboot will not support these platforms unless further testing resolves the issue. ### Source excerpt Article: ThinkPad X201 support removed from Libreboot Web link: https://libreboot.org/news/x201.html ## Using tar and SSH as an alternative to rsync for transferring files DevFeed: [Using tar and SSH as an alternative to rsync for transferring files]() Original publisher: [Read original article]() Author: March Published: 2026-03-28T00:00:00Z Content type: tutorial Language: en Sources: [Drew DeVault]() Topics: [rsync](), [Command-line interface](), [ssh](), [Compression]() Tags: [command-line](), [compression](), [how-to](), [rsync](), [ssh]() ### AI overview The article explains how to use tar piped through SSH to transfer files to another host, preserving ownership and permissions while using gzip compression. It notes that tar does not identify and skip files that are already up to date, unlike rsync, and presents basic tar options and an optional progress display with pv. ### Source excerpt So apparently rsync is slop now. When I heard, I wanted to drop a quick note on my blog to give an alternative: tar. It doesn't do everything that rsync does, in particular identifying and skipping up-to-date files, but tar + ssh can definitely accomodate the use case of "transmit all of these files over an SSH connection to another host". Consider the following: tar -cz public | ssh example.org tar -C /var/www -xz This will transfer the contents of ./public/ to example.org:/var/www/public/, preserving file ownership and permissions and so on, with gzip compression. This is roughly the equivalent of: rsync -a public example.org:/var/www/ Here's the same thing with a lightweight progress display thanks to pv: tar -cz public | pv | ssh example.org tar -C /var/www -xz I know tar is infamously difficult to remember how to use. Honestly, I kind of feel that way about rsync, too. But, here's a refresher on the most important options for this use-case. To use tar, pick one of the following modes with the command line flags: -c: create an archive -x: extract an archive Use -f to read from or write to a file. Without this option, tar uses stdin and stdout, which is what the pipelines above rely on. Use -C to change directories before archiving or extracting files. Use -z to compress or decompress the tarball with gzip. That's basically everything you need to know about tar to use it for this purpose (and for most purposes, really). With rsync, to control where the files end up you have to memorize some rules about things like whether or not each path has a trailing slash. With tar, the rules are, in my opinion, a bit easier to reason about. The paths which appear on the command line of tar -c are the paths that tar -x will open to create those files. So if you run this: tar -c public/index.html public/index.css You get a tarball which has public/index.html and public/index.css in it. When tar -x opens this tarball, it will call fopen("public/index.html", "w ## Comandos esenciales de LVM: guía rápida DevFeed: [Comandos esenciales de LVM: guía rápida]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-02-20T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [LVM](), [Linux](), [backups](), [Mdadm](), [RAID](), [rsync](), [Homelab]() Tags: [backups](), [homelab](), [libre](), [linux](), [lvm](), [mdadm](), [raid](), [rsync]() ### AI overview A Spanish-language cheat sheet covering essential LVM commands for managing physical volumes, volume groups, and logical volumes on Linux. It explains common workflows such as extending volumes and filesystems, creating and reducing volumes, migrating data, and creating snapshots for backups. ### Source excerpt Cheatsheet con los comandos más usados de LVM (Logical Volume Manager) para la gestión de volúmenes lógicos en Linux. ## Vagrant: entornos de desarrollo reproducibles DevFeed: [Vagrant: entornos de desarrollo reproducibles]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-02-06T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Vagrant](), [Oracle-VM-VirtualBox](), [Linux]() Tags: [ansible](), [hashicorp](), [rsync](), [ruby](), [snapshots](), [vagrant](), [virtualbox]() ### AI overview A Spanish tutorial explaining how Vagrant defines reproducible development environments as code. It covers installation, provider selection, Vagrantfile configuration, the VM lifecycle, SSH access, and synchronized folders, including performance and consistency considerations for VirtualBox, libvirt, NFS, and rsync. ### Source excerpt Vagrant con libvirt o VirtualBox: carpetas sincronizadas, snapshots, aprovisionamiento con Ansible y reload vs provision. ## Backups incrementales con rsync en Linux DevFeed: [Backups incrementales con rsync en Linux]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-01-16T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [backups](), [rsync](), [Linux](), [Script](), [ssh](), [systemd]() Tags: [backup](), [backups](), [filesystem](), [incremental](), [linux](), [nas](), [rsync](), [ssh](), [systemd]() ### AI overview A tutorial on implementing incremental backups with rsync and hardlinks on Linux servers. It explains how unchanged files are hardlinked to save space, warns that hardlinks are not independent copies, discusses filesystem compatibility and destructive synchronization risks, and covers SSH transfers, exclusions, systemd timers, and integrity checks. ### Source excerpt Cómo implementar una estrategia de backups incrementales usando rsync y hardlinks para ahorrar espacio y tiempo en tus servidores. ## 10 scripts Bash útiles para sysadmins DevFeed: [10 scripts Bash útiles para sysadmins]() Original publisher: [Read original article]() Author: Alois Published: 2026-01-14T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Scripting, bash](), [Bash](), [backups](), [monitor](), [rsync]() Tags: [backups](), [bash](), [logs](), [rsync](), [script](), [scripts](), [shell](), [sysadmin](), [sysadmins]() ### AI overview A Spanish-language tutorial presents ten practical Bash scripts for system administrators, including disk monitoring, rotating backups, log cleanup, and other routine tasks. It notes that Bash scripts suit focused tasks on individual machines but are not a replacement for configuration-management tools when managing many servers. ### Source excerpt Colección de scripts Bash prácticos para monitorización, backups, limpieza de logs y tareas comunes de administración de sistemas. ## Mitigating a rsync Vulnerability: A Lesson in Compiler Hardening DevFeed: [Mitigating a rsync Vulnerability: A Lesson in Compiler Hardening]() Original publisher: [Read original article]() Published: 2025-03-19T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Compiler](), [chainguard](), [Security](), [c/c++](), [vulnerability]() Tags: [c](), [c-plus-plus](), [chainguard](), [compiler-flags](), [compiler-hardening](), [cves](), [defense-in-depth](), [hardening](), [linux](), [llvm](), [product-security](), [rsync](), [security](), [x86-64]() ### AI overview Chainguard describes how compiler hardening in its C/C++ toolchain helped protect against an rsync vulnerability before public disclosure. The article presents compiler hardening flags as layers of defense for memory-unsafe software and discusses Chainguard's implementation of recommendations from OpenSSF and GCC. ### Source excerpt Chainguard's defense-in-depth security strategy protected against multiple rsync CVEs before they were even reported. See how we did it, using compiler flags. ## What to do about SQLITE\_BUSY errors despite setting a timeout DevFeed: [What to do about SQLITE\_BUSY errors despite setting a timeout]() Original publisher: [Read original article]() Published: 2025-02-16T20:00:00Z Content type: tutorial Language: en Sources: [Bert Hubert's writings]() Topics: [SQLite](), [Concurrency](), [PostgreSQL]() Tags: [errors](), [postgresql](), [programming](), [rsync](), [sqlite](), [timeout]() ### AI overview This article explains why SQLite can return SQLITE_BUSY despite a configured timeout. It recommends avoiding read-to-write transaction upgrades and using BEGIN IMMEDIATE, or starting the transaction with a write, while describing the concurrency behavior involved. ### Source excerpt So I'm a huge SQLite fanboy and I use it for almost everything these days. Recently, the project added sqlite3_rsync which allows you to swiftly replicate your database to other servers (or to the same server if you want), and this really was the cherry on top for me. Last week however, I ran into one of my projects unexpectedly getting SQLITE_BUSY errors. And then someone urged me to run 'a real database' (PostgreSQL), and that hurt. ## Restrict SSH to rsync for deploying files with GitHub Actions DevFeed: [Restrict SSH to rsync for deploying files with GitHub Actions]() Original publisher: [Read original article]() Author: Schakko Published: 2020-07-20T07:32:08Z Content type: tutorial Language: en Sources: [Schakko]() Topics: [GitHub Actions](), [rsync](), [Security](), [ssh](), [Deployment]() Tags: [ci-cd](), [deployment](), [github](), [github-actions](), [public-key](), [rsync](), [security](), [ssh]() ### AI overview This tutorial explains how to restrict rsync access over SSH when deploying a GitHub repository with GitHub Actions. It presents a custom SSH wrapper script and the official Perl-based rrsync script, including read-only or write-only restrictions for a specified directory. ### Source excerpt rsync access can be restricted with a custom wrapper script or an official script named "rrsync". Access to your remote filesystem should always be restricted so you won't leak any information in case of a security breach. I've used GitHub Actions a lot in the last few months. For web [...] The post Restrict SSH to rsync for deploying files with GitHub Actions appeared first on schakko.de. ## SCP Overview: Familiar, Simple, Insecure and Slow DevFeed: [SCP Overview: Familiar, Simple, Insecure and Slow]() Original publisher: [Read original article]() Author: info@goteleport.com (Andrew Lytvynov) Published: 2020-06-18T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [Software](), [ssh](), [OpenSSH](), [rsync](), [Unix](), [Authentication](), [Encryption]() Tags: [authentication](), [encryption](), [how-to](), [openssh](), [rsync](), [security](), [ssh](), [unix]() ### AI overview This technical overview explains SCP as a widely available file-transfer tool that operates over SSH. It describes SCP's historical and nonstandard implementation, with SSH providing authentication and encryption, and notes that newer tools such as SFTP and rsync can outperform it. ### Source excerpt SCP is a simple tool with a quirky implementation. It does an okay job at moving files around, but newer software like SFTP and Rsync outperforms it. ## Removing Google as a Single Point of Failure Part 2: Gmail DevFeed: [Removing Google as a Single Point of Failure Part 2: Gmail]() Original publisher: [Read original article]() Published: 2020-03-18T00:00:00Z Content type: article Language: en Sources: [Jake Wharton]() Topics: [Google](), [data](), [DRIVE](), [Homelab]() Tags: [backing-up](), [data](), [google](), [home-server](), [rsync](), [security]() ### AI overview The article explains how to reduce dependence on Google as a single point of failure while continuing to use Google services as the source of truth. It covers backing up Google Photos and Google Drive to a home server and rsync.net, then describes using a custom domain and Fastmail to preserve email access and support catch-all addresses. ### Source excerpt I want to remove Google as a single point of failure in my life. In the first blog post on this subject I detailed my setup for backing up Google Photos and Google Drive contents onto my home server and remotely to rsync.net. Left out of that post was a solution for Gmail because I hadn't found one yet. Now I have. Source of truth That first post started with an important qualification: This does not mean that I'm going to stop using Google products. Quite the opposite. Gmail, Google Photos, and Google Drive will remain the source-of-truth for all of the things I listed above. What's different is that should Google disappear tomorrow (or just my account) I would lose no data. This was easy to achieve with Photos and Drive because the data is all there is. With email that's unfortunately not true. Incrementally backing up the email data is pretty straightforward-we'll get into that shortly. But with Gmail your email address is still tied to the @gmail.com domain. So if my account or all of Google disappears, I won't be able to receive any more email. Of course the "easy" fix here is to just use a domain that I control. Obviously I own jakewharton.com, and I intend to set that up, but I wanted something shorter. I've owned cob.io for many years with the intention of setting up j@cob.io, but I go by "Jake". Luckily the last few years have seen an influx of new TLDs so I managed to grab ke.fyi. Say hello to j@ke.fyi! Having an email on my own domain doesn't address the problem that there's still hundreds or thousands of services that I've given the Gmail address to. While I can migrate many, there are inevitably those which I can't or that I simply don't know exist. The old address needs to remain working. Fastmail After browsing a few hosted email solutions, I settled on Fastmail (Note: referral link). In addition to a positive recommendation from a friend, there were a few key motivating factors. Domain catch-all A popular feature of Gmail is the ability to append a + ## Extracting 100% of Data From a Stubborn, Dying ZFS Pool DevFeed: [Extracting 100% of Data From a Stubborn, Dying ZFS Pool]() Original publisher: [Read original article]() Published: 2020-02-12T00:00:00Z Content type: article Language: en Sources: [Jake Wharton]() Topics: [data](), [Homelab](), [Hardware](), [IO](), [Kernel](), [Processes](), [Software](), [ssh](), [Ubuntu]() Tags: [data](), [hardware](), [home-server](), [kernel](), [orchestration](), [process](), [rsync](), [server](), [software](), [ssh](), [ubuntu]() ### AI overview The article describes recovering all data from a deteriorating ZFS pool built from ten-year-old hard drives. During migration to a new server, drive read failures and pool lockups caused rsync transfers to enter uninterruptible sleep in the I/O stack, requiring repeated hard reboots and extending the estimated transfer time from four days to approximately twelve. ### Source excerpt In 2010 I built a home server with five 2TB drives. It ran Solaris and ZFS for the redundancy and data checksumming to ensure no data could be lost or corrupted. Just 16 months later five 3TB drives were added to the pool. This computer took the 2600-mile trip to live in San Francisco with me. It then endured the 2600-mile return trip when I left. Having sat unplugged for five years, I recently powered the server back on for new workloads. But relying on 10 ten-year-old hard drives in 2020 is asking for cascading failure. And not only were the drives old, they've experienced physical trauma. So instead I built a new server and endeavored to migrate the data. During the transfer the drives exhibited consistent read failures as expected, but ZFS was able to transparently mitigate them. Occasionally, though, the pool would lock up in a way that could only be fixed with a hard reboot. These lock ups sent me on a weird journey of software and hardware orchestration to complete the data transfer. Symptoms During transfer of the data, progress would stall randomly in a way that seemingly could not be killed. CTRL+C had no effect. No kill signal had an effect. Even last-resort shutdown -r nows did nothing. The system was oddly otherwise responsive. You could SSH in from another tab and poke around. ps showed that the transfer process was in the "D+" state which was uninterruptible sleep in the foreground. jake 21749 1.1 0.0 8400 2124 pts/0 D+ 23:42 0:00 rsync ... That explained why the process wouldn't die. The dmesg output also confirmed the problem happened deep in the I/O stack. [ 3626.101527] INFO: task rsync:30680 blocked for more than 120 seconds. [ 3626.101547] Tainted: P O 5.3.0-26-generic #28-Ubuntu [ 3626.101563] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3626.101580] rsync D 0 30680 1 0x00000000 [ 3626.101584] Call Trace: [ 3626.101590] __schedule+0x2b9/0x6c0 [ 3626.101596] schedule+0x42/0xb0 [ 3626.101601] schedule_timeout+0x152/ ## \[Linux\] Simplest possible snapshot-style backups using rsync DevFeed: [\[Linux\] Simplest possible snapshot-style backups using rsync]() Original publisher: [Read original article]() Published: 2019-10-15T22:00:00Z Content type: tutorial Language: en Sources: [Dennis Yurichev]() Topics: [Linux](), [rsync](), [Script](), [ransomware]() Tags: [backup](), [backups](), [linux](), [ls](), [malware](), [ransomware](), [rsync](), [script]() ### AI overview A tutorial for creating snapshot-style backups on Linux with rsync, hard links, and dated directories. It explains how snapshots preserve file history, conserve disk space by storing unchanged files only once, and allow older versions to remain available after deletion or ransomware encryption. ### Source excerpt [Linux] Simplest possible snapshot-style backups using rsync ## Prometheus authentication with oauth2\_proxy DevFeed: [Prometheus authentication with oauth2\_proxy]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2018-05-28T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Prometheus](), [OAuth 2.0](), [proxy](), [nginx](), [Grafana](), [Authentication](), [Docker Compose](), [rsync](), [GitHub]() Tags: [authentication](), [docker-compose](), [github](), [grafana](), [nginx](), [oauth2](), [prometheus](), [proxy](), [rsync]() ### AI overview A tutorial showing how to put Prometheus, Grafana, and Alertmanager behind nginx and oauth2_proxy, using GitHub authentication and a Docker Compose-based setup. ### Source excerpt I wanted to set up a prometheus machine for me to monitor random stuff, but I was always postponing that because I didn't want to use SSH port-forwarding, firewalls, create a VPC and/or setup an OpenVPN server or anything like that. ## Backing up with Capistrano DevFeed: [Backing up with Capistrano]() Original publisher: [Read original article]() Author: Keith Smiley Published: 2013-01-05T20:12:00Z Content type: tutorial Language: en Sources: [Keith Smiley]() Topics: [Automation](), [Linode](), [hosting](), [Server](), [Bash]() Tags: [automated](), [automation](), [backing-up](), [backup](), [bash](), [dropbox](), [hosting](), [linode](), [local](), [os](), [rsync](), [server]() ### AI overview A tutorial on using Capistrano to automate weekly backups from a Linode-hosted web server to a local machine. It creates a compressed tarball remotely, downloads it with scp, stores it in Dropbox, and schedules the task through local cron. ### Source excerpt We all know not backing up has consequences. While losing sentimental files would definitely ruin your day, losing your web server's data could be even worse. I've mentioned before that I use Linode for my server hosting, and while they do offer an automated backup service I decided I'd rather setup my own solution to back up periodically to my local machine. Many people use rsync to do their server backups. In fact Linode even has a guide on how to set it up (there's a better one here). I decided that instead of a 1 for 1 directory backup, I would prefer to have a tarball of the contents. While I could've easily done this with a few bash commands from the server that's not particular ideal for my setup. My local machines don't run 24/7 so if I set it up on the server to automate the backup every week, it may try to initiate the backup when my machine was off (I could try to guess when it's on every week but that's not ideal either). The obvious solution to this is run it from my local machine instead every week. That way once a week when it's powered up it would log in to the server, create the tarball and pull it down. Insert Capistrano ([sudo] gem install capistrano) a RubyGem for 'Remote multi-server automation.' So I wrote a very basic Capfile to automate this for me (replace the path to your www folder accordingly). load 'deploy' $SERVER_USER = "username" $SERVER_IP = "1.1.1.1" desc "Backs up server www files" task :backup, :hosts => $SERVER_IP do run "cd /srv; tar -pvczf ~/backup.tar.gz www/" run_locally "scp #{ $SERVER_USER }@#{ $SERVER_IP }:~/backup.tar.gz ~/Dropbox/Backups/Server" end Then I added this to my crontab on my local machine by running crontab -e and adding the line: @weekly /Users/ksmiley/.rbenv/shims/cap -f ~/path/to/Capfile backup I included the path to the Capistrano executable since cron (on OS X) executes tasks with sh, which isn't setup with my $PATH. ## Automatyczne backupy w stylu snapshot z rsync'iem DevFeed: [Automatyczne backupy w stylu snapshot z rsync'iem]() Original publisher: [Read original article]() Author: Tom Published: 2011-12-29T00:00:00Z Content type: tutorial Language: pl Sources: [Tomasz Gągor]() Topics: [rsync]() Tags: [backup](), [rsync]() ### AI overview The article discusses snapshot-style backups using rsync as an alternative to compressed full, differential, and incremental backups, whose restoration process can be slow and cumbersome. The author says they developed a backup script based on another article. ### Source excerpt Można znaleźć wiele tutoriali jakimi narzędziami wykonywać backupy. W większości przypadków absolutnie wystarczający okaże się flexbackup. Bardziej wymagający wykorzystają BackupPC, Baculę lub Amandę. Narzędzia te pozwalają wykonać kopie pełne, różnicowe, przyrostowe - kompresując je dla zaoszczędzenia miejsca. Wszystko fajnie - ale problemy pojawiają się przy dostępie do tych danych. Żeby odzyskać plik zmodyfikowany dzisiaj trzeba rozpakować najpierw kopię pełną, potem różnicową, przyrostową by wreszcie wyciągnąć plik z wczoraj... hmm ten też jest skopany. No to lecimy jeszcze raz... ## Emacs Muse hacking DevFeed: [Emacs Muse hacking]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2010-03-04T12:33:00Z Content type: tutorial Language: en Sources: [Dimitri Fontaine]() Topics: [Emacs](), [Code](), [HTML](), [rsync](), [Shell]() Tags: [code](), [emacs](), [html](), [rsync](), [shell]() ### AI overview An Emacs Muse user explains how to customize the publishing process to generate one file per blog article and add an index of previous articles. The article describes using Muse output-buffer functions and provides code that requires manual editing for customization. ### Source excerpt Now you know what piece of software is used to publish this blog. I really like it, the major mode makes it a great experience to be using this tool, and the fact that you produce the HTML and rsync it all from within Emacs ( C-c C-p then C-c C-r with some easy elisp code) is a big advantage as far as I'm concerned. No need to resort to shell and Makefile. ## Emacs Muse based publishing DevFeed: [Emacs Muse based publishing]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2009-10-06T15:23:00Z Content type: tutorial Language: en Sources: [Dimitri Fontaine]() Topics: [Emacs](), [rsync](), [Command-line interface]() Tags: [command-line](), [emacs](), [muse](), [rsync]() ### AI overview An Emacs Muse publishing workflow uses an interactive Emacs command to publish a blog with rsync, including optional synchronization of static CSS, image, and PDF directories. ### Source excerpt As you might have noticed, this little blog of mine is not compromising much and entirely maintained from Emacs. Until today, I had to resort to term to upload my publications, though, as I've been too lazy to hack up the tools integration for simply doing a single rsync command line. That was one time to many: (defvar dim:muse-rsync-options "-avz" "rsync options") (defvar dim:muse-rsync-source "~/dev/muse/out" "local path from where to rsync, with no ending /") (defvar dim:muse-rsync-target "dim@tapoueh.org:/home/www/tapoueh.org/blog.tapoueh.org" "Remote URL to use as rsync target, with no ending /") (defvar dim:muse-rsync-extra-subdirs '("../css" "../images" "../pdf") "static subdirs to rsync too, path from dim:muse-rsync-source, no ending /") (defun dim:muse-project-rsync (&optional static) "publish tapoueh.org using rsync" (interactive "P") (let* ((rsync-command (format "rsync %s %s %s" dim:muse-rsync-options (concat dim:muse-rsync-source "/") (concat dim:muse-rsync-target "/")))) (with-current-buffer (get-buffer-create "*muse-rsync*") (erase-buffer) (insert (concat rsync-command "\n")) (message "%s" rsync-command) (insert (shell-command-to-string rsync-command)) (insert "\n") (when static (dolist (subdir dim:muse-rsync-extra-subdirs) (let ((cmd (format "rsync %s %s %s" dim:muse-rsync-options (concat dim:muse-rsync-source "/" subdir) dim:muse-rsync-target))) (insert (concat cmd "\n")) (message "%s" cmd) (insert (shell-command-to-string cmd)) (insert "\n"))))))) (define-key muse-mode-map (kbd "C-c R") 'dim:muse-project-rsync) So now to publish this blog, it's just a C-c R away! :)