iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
etckeeper puts a Linux machine’s /etc directory under version control so you can see configuration changes, identify when they happened, and restore an earlier state. Install it from your distribution, verify the configured version-control backend, review changes before committing, and validate services after any rollback. On Ubuntu, installation normally initializes the repository and creates the first commit automatically.
This is host-local history, not a complete fleet-management or secret-management system. Treat the repository and every copy of it as sensitive because /etc can contain credentials, private keys, ownership rules, permissions, and security policy.
What etckeeper does—and what it does not do
Linux configuration is spread across files in /etc. Package upgrades, administrator edits, provisioning scripts, and service installers can all change those files. Without history, a broken change is difficult to attribute and a known-good version may be hard to reconstruct.
etckeeper adds a version-control workflow around that directory. It initializes a repository, records file changes, preserves metadata that ordinary Git does not normally handle, and provides a wrapper that runs the configured version-control system from /etc. The upstream project describes the result as using Git to review or revert changes made to /etc.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application:Upgraded attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Warranty & Support: Our Electric air duster comes with 5 years warranty and 24/7 customer service. During this period, if you have any questions,pls kindly feel free to contact us.
- Auditability: history shows which files changed and when. Manual commits can include a reason, and etckeeper records the original username when a user became root through
sudoorsu. - Recovery: you can compare a current file with an earlier commit and restore a selected version.
- Package visibility: package-manager hooks create snapshots around package operations, so configuration changes introduced by an upgrade appear in history.
- Metadata awareness: etckeeper tracks attributes such as permissions that are security-sensitive for files including
/etc/shadow.
It does not redact passwords, encrypt repository contents, test whether a service will accept a restored configuration, or reproduce an entire host. A remote push is useful for a protected backup copy, but it is not by itself a disaster-recovery plan.
Install etckeeper on Debian or Ubuntu
1. Install the distribution package
On a Debian- or Ubuntu-based host, update package indexes and install the package as root:
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →sudo apt update
sudo apt install etckeeperUse the distribution package rather than copying an arbitrary script into /etc; package integration supplies the hooks that connect etckeeper with the package manager and the system’s scheduled maintenance.
2. Confirm initialization and the backend
Ubuntu documents that installing etckeeper automatically initializes /etc and creates an initial commit. The main configuration file is:
/etc/etckeeper/etckeeper.confUbuntu uses Git as the default version-control backend. Do not assume that setting on another distribution or an older installation: open the configuration file and identify the selected VCS before using backend-specific commands.
Immediately check the working tree and recent history:
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchsudo etckeeper vcs status
sudo etckeeper vcs log --oneline --decorate -n 10The vcs subcommand invokes the configured VCS command in /etc. A clean status after installation means the initial snapshot has captured the current configuration. An uncommitted status is not an installation failure; it means files changed during or after initialization and need review.
3. Remove initialization only when you have a documented reason
Ubuntu documents this command for removing etckeeper’s initialization:
sudo etckeeper uninitBefore running it, preserve any history or backup required by your operating procedure and record why version tracking is being removed. Uninitializing eliminates the normal etckeeper workflow for that host, so later recovery and auditing will no longer have the same baseline.
Understand the repository’s operating model
The initial commit is a baseline, not a change explanation
The installation-time commit captures the state that existed when etckeeper was initialized. It gives you a comparison point, but it cannot explain edits that happened before installation. Add meaningful manual commits after that baseline so future reviewers can distinguish an intentional hardening change from an incidental package edit.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
Automatic coverage and deliberate commits serve different purposes
By default, Ubuntu’s integration makes daily commits of uncommitted /etc changes and creates commits before and after package installation. Those automatic snapshots reduce the chance that an unrecorded change disappears from history.
Automatic commits usually lack the operational context a human can provide. For a planned edit, inspect the diff and make an explicit commit with a message. That creates a durable explanation while retaining the automatic snapshots as surrounding evidence.
Metadata is part of the configuration state
Ordinary Git does not normally preserve every file attribute that matters on a Unix system. etckeeper extends the workflow to track metadata such as permissions. This is important for security-sensitive files: a content-only comparison could miss a mode or ownership change that affects who can read or modify a file.
The scope is one host’s evolving /etc
etckeeper is designed to follow the configuration state of an individual machine. It is valuable for local audit trails, review, and recovery from accidental edits. It is not a substitute for a protected source repository, a configuration-management system, a secrets manager, host rebuild documentation, or tested disaster recovery.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Use a deliberate edit-and-commit workflow
1. Establish the starting point
Before changing a file, check whether earlier work is already uncommitted:
sudo etckeeper vcs status
sudo etckeeper vcs log --oneline --decorate -n 10If the tree is already dirty, inspect those changes before adding your own. Mixing unrelated work in one commit makes later attribution and rollback harder.
2. Edit with the normal administrative tool
For example, edit the SSH daemon configuration with sudoedit:
sudoedit /etc/ssh/sshd_configUse the editor, package utility, or service-specific tool appropriate to the file. etckeeper does not replace validation rules for the service that consumes the configuration.
Recommended Free Tools
3. Inspect the exact diff
Review the file before committing it:
sudo etckeeper vcs diff -- /etc/ssh/sshd_configLook for unintended whitespace changes, duplicated directives, removed defaults, generated secrets, and permission or ownership changes. If the diff contains unrelated edits, separate them or document why they belong together.
4. Commit with an operational reason
When the diff is understood, create a deliberate commit:
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
sudo etckeeper commit 'Harden SSH authentication settings'etckeeper commit [message] commits all current /etc changes, not only the file you just viewed. That makes the pre-commit status check important. The commit message should identify the purpose, ticket, maintenance window, or security decision that a future operator will need.
5. Verify the resulting state
Confirm that the working tree is clean and that the new commit is visible:
sudo etckeeper vcs status
sudo etckeeper vcs log --oneline --decorate -n 3Then run the affected service’s configuration checker and status procedure before declaring the change complete. For example, an SSH configuration change should pass the daemon’s syntax test before you reload it; a web-server change should pass that server’s configuration test before a reload. Keep the service’s normal validation and rollback procedure alongside the etckeeper commands.
How automatic commits expose package changes
Daily commits
Ubuntu documents daily commits of uncommitted /etc changes by default. This is a safety net for edits made by scripts, installers, or administrators who did not make a manual commit. It is not a replacement for meaningful commit messages.
The setting AVOID_DAILY_AUTOCOMMITS disables this behavior. Leave automatic coverage enabled unless your operating procedure supplies another reliable schedule and identifies who is responsible for the replacement. If daily snapshots are disabled, a forgotten change can remain unrecorded until a package operation or manual commit happens.
Before-and-after package snapshots
APT hooks create commits before and after package installation. To see the effect, Ubuntu’s guide demonstrates installing the postfix package and then examining the resulting history. Configuration files changed by the package operation appear in the surrounding commits, allowing you to separate pre-existing edits from package-provided changes.
Free tools Windows power users keep installed
One-click scans. No signup required.
sudo apt install postfix
sudo etckeeper vcs log --oneline --decorate -n 10
sudo etckeeper vcs statusA package transaction can touch many files, including files that are regenerated or updated as dependencies are configured. Review the commit contents rather than assuming every changed line was directly edited by the package named in the command.
Reading package-related history
Use the log to find the relevant snapshot, then compare adjacent commits:
sudo etckeeper vcs log -- /etc
sudo etckeeper vcs diff HEAD~1..HEAD -- /etcFor a narrower review, replace /etc with the service directory or file you care about. If the package operation produced both a before and an after commit, comparing those commits shows the net configuration change while preserving the earlier baseline.
Answer “what changed?” before reverting anything
Review a service directory’s history
To inspect changes affecting Nginx configuration, for example:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
sudo etckeeper vcs log -- /etc/nginxHistory can reveal whether a file changed in a manual hardening commit, a package transaction, a daily snapshot, or a maintenance script. Use the commit message and timestamp as context, then inspect the actual patch.
Compare two known points
sudo etckeeper vcs diff HEAD~1..HEAD -- /etc/nginxThe two endpoints can be any commits supported by the configured backend. Choose them deliberately: comparing the current tip with its parent answers a different question from comparing the current state with the installation baseline.
Attribute individual lines
sudo etckeeper vcs blame /etc/ssh/sshd_configBlame identifies the commit associated with each line, which helps locate the change that introduced a setting. Treat it as an investigative aid, not proof that the named author was the person who originally designed the policy; automated commits and package hooks can also produce history.
Roll back a bad configuration change safely
A version-control restore writes files back into the live /etc directory. It is not a dry run and it does not automatically restart, reload, or validate a service. Use this sequence whenever possible.
- Stabilize the incident. If a service is failing, capture its current status and logs through your normal operations process. Avoid making several unrelated edits while you are still identifying the cause.
- Find the known-good commit. Use
log,diff, and, where useful,blameto identify the last state that was known to work. Do not guess based only on the newest commit. - Preview the difference. Compare the current file with that commit and confirm that the proposed restore addresses the actual fault.
- Restore only the necessary path. From
/etc, use the checkout or restore command provided by the configured backend. With a Git backend, a single-file restore has this form:
sudo etckeeper vcs checkout <known-good-commit> -- /etc/nginx/nginx.confReplace the placeholder with the selected commit identifier and use the backend’s equivalent command if the host is not using Git. Restoring an entire directory has a larger blast radius than restoring one file, so scope the path to the smallest set that fixes the incident.
- Inspect the post-restore diff. Confirm exactly what changed and check whether permissions or ownership were restored along with file contents:
sudo etckeeper vcs diff -- /etc/nginx/nginx.conf- Validate the service. Run the service’s syntax checker, inspect its status, and reload or restart it only through the normal procedure. A configuration that matches an old commit can still be incompatible with the currently installed software version or the current runtime state.
- Commit the recovery decision. If the restored state is the intended operating state, record it:
sudo etckeeper commit 'Restore known-good Nginx configuration'That commit distinguishes an intentional recovery from an unexplained reversal. If you restored temporarily while investigating, document the temporary state and its follow-up rather than leaving an ambiguous dirty tree.
Customize hooks and maintenance behavior
Use command-specific hook directories
The upstream project runs executable files in /etc/etckeeper/$command.d/. This provides a controlled place for integrations that should run at a particular etckeeper lifecycle stage. Keep hooks short, auditable, and failure-aware; a hook that silently changes backup or commit behavior can undermine the audit trail.
Examples documented by the upstream project
- A post-install hook can run
git gcto maintain the Git repository. - Disabling
commit.d/50vcs-commitstops automatic commits while retaining file-staging behavior. Use this only when another documented process creates commits reliably. - A commit hook can run
git push backupto a configured clone.
The last example is Git-specific. Verify the remote name, authentication method, failure handling, and destination access controls before enabling it on a production host.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsDistinguish backup transport from disaster recovery
Pushing commits to a remote protects against loss of the local repository, but it does not recreate the operating system, packages, network identity, data volumes, secrets, or service dependencies. Document how to rebuild the host, how to retrieve the protected repository, and how to restore it without exposing credentials. Test that procedure in an environment appropriate to the service instead of assuming a successful push proves recoverability.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Protect /etc history and remotes
Configuration history can be more sensitive than the current file tree because old values remain available for inspection. A previous commit may contain a password, a private key, a database connection string, access-control policy, or a hostname that should no longer be public.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
- Keep local repository permissions restrictive and limit shell access to administrators who need the history.
- Use an access-controlled private remote when copying the repository.
- Use encrypted transport and encrypted storage for remote copies; etckeeper and Git do not automatically provide secret redaction.
- Review hooks and backup jobs for accidental logging of credentials or repository contents.
- If a secret is committed, treat it as exposed: rotate or revoke it, then follow your organization’s approved history-removal and remote-cleanup procedure. Deleting the current working copy does not remove an earlier commit.
Do not place a repository containing /etc history in an unrestricted public location. The convenience of remote review is not worth making machine credentials or security policy broadly readable.
Choose the right scope for your environment
Three operating patterns cover most deployments. The choice depends on whether you need to recover one machine, protect history off-host, or reproduce configuration across many machines.
| Approach | Recovery scope | Secret-exposure controls | Audit detail | Automation burden | Rollback blast radius | Reproduce a host from scratch |
|---|---|---|---|---|---|---|
| Local etckeeper repository only | One host, while its storage remains available | Restrictive local permissions; no remote copy to secure | Strong file and metadata history on that host; manual messages improve context | Low after package installation and scheduler integration | Can be limited to selected files or directories | No; it does not contain the operating system and full host build process |
| etckeeper plus a pushed private remote | One host’s configuration history survives local loss | Requires private access controls, encrypted transport and protected remote storage | Same host-local history, with an off-host copy | Moderate; remote authentication, hooks and failure monitoring must be maintained | Still host-level, but a mistaken restore can alter live service configuration | Not by itself; rebuild instructions and other backups are still required |
| Configuration-management workflow paired with etckeeper | Fleet-wide desired state plus per-host history | Central policy and secret-management controls must be designed separately | Central change review plus local evidence of package and runtime edits | Highest; requires source control, testing, enrollment and drift handling | Potentially fleet-wide if a bad change is promoted broadly, so staged rollout is essential | Best of the three when the management code, package inputs and recovery process are maintained |
For a single server, local etckeeper may be sufficient for accidental-edit recovery. Add a protected remote when loss of the host would also lose the only copy of history. For many hosts, use a reviewed configuration-management source of truth and keep etckeeper as host-level evidence of what actually happened, including package-driven drift.
Troubleshoot common problems
The backend is not Git
Read /etc/etckeeper/etckeeper.conf and use sudo etckeeper vcs status rather than assuming Git syntax. The wrapper is intentionally backend-neutral for routine status, history, and diff operations; checkout, restore, remote, and hook commands may differ.
The working tree is unexpectedly dirty
Run a targeted diff and inspect the most recent commits:
sudo etckeeper vcs status
sudo etckeeper vcs diff
sudo etckeeper vcs log --oneline --decorate -n 10Common explanations include a package transaction, a scheduled daily snapshot boundary, a service installer, a generated file, or an administrator edit made outside the expected maintenance window. Do not commit blindly; identify the source and decide whether the change should be retained.
No daily commits appear
Check whether AVOID_DAILY_AUTOCOMMITS is enabled and verify that the distribution’s scheduler and etckeeper maintenance integration are operating. If your policy intentionally disables daily commits, document the replacement schedule and test that it creates usable history.
A package upgrade produced a large diff
Inspect the before-and-after package commits and narrow the diff to the affected service directory. Package configuration scripts can update defaults, regenerate files, or touch dependency configuration. Separate expected package changes from local policy edits before committing additional adjustments.
A restore fixed the file but not the service
Check syntax, ownership, permissions, dependent files, environment variables, and the service’s runtime logs. The historical file may have been valid for an earlier package version or may depend on another file that was changed later. etckeeper restores tracked state; it cannot prove that the complete running service state matches that historical point.
A remote push fails
Keep the local commit; a failed push does not erase it. Check remote reachability, credentials, host-key verification, permissions, and repository capacity. Retry only after confirming that the destination is the intended private remote and that failure notifications will not leak repository contents.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A practical operating policy
Adopt a short written policy so every administrator handles /etc consistently:
- Install etckeeper from the distribution package and verify the selected backend.
- Retain the automatic daily and package-manager coverage unless an approved alternative exists.
- Before a planned edit, check status, edit with the normal tool, inspect the targeted diff, and commit all intended changes with a reason.
- For investigations, use log, diff, and blame before choosing a rollback point.
- Restore the smallest necessary path, inspect the resulting diff, validate the service, and record the recovery decision.
- Restrict local access and protect every remote copy with private access controls and encryption.
- Document host rebuild and restoration steps separately; test them instead of treating a remote push as proof of disaster recovery.
With that discipline, etckeeper turns an opaque stream of edits in /etc into a reviewable timeline while leaving service validation, secret protection, fleet policy, and full-host recovery where they belong: in your operational procedures.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
