<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Etc on Linux Security</title><link>https://linuxtransfer.com/tags/etc/</link><description>Recent content in Etc on Linux Security</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 25 Sep 2026 09:17:26 +0200</lastBuildDate><atom:link href="https://linuxtransfer.com/tags/etc/index.xml" rel="self" type="application/rss+xml"/><item><title>Recovering a Deleted /etc Directory on a VPS with Borg Snapshot Restore</title><link>https://linuxtransfer.com/post/2026-09-25-recovering-a-deleted-etc-directory-on-a-vps-w/</link><pubDate>Fri, 25 Sep 2026 09:17:26 +0200</pubDate><guid>https://linuxtransfer.com/post/2026-09-25-recovering-a-deleted-etc-directory-on-a-vps-w/</guid><description>&lt;p>When a VPS loses its &lt;code>/etc&lt;/code> directory, the system can become unbootable or at least unusable until the configuration files are restored. If you have been running Borg backups (the recommended tool for incremental, deduplicated snapshots) the recovery path is clear: locate the snapshot that contains the last good &lt;code>/etc&lt;/code>, extract it, and replace the missing directory. This walkthrough shows the exact commands, trade‑offs, and security checks you should perform on a current 2026 VPS environment.&lt;/p></description></item></channel></rss>