this post was submitted on 08 Aug 2023
16 points (100.0% liked)

linux4noobs

1340 readers
1 users here now

linux4noobs


Noob Friendly, Expert Enabling

Whether you're a seasoned pro or the noobiest of noobs, you've found the right place for Linux support and information. With a dedication to supporting free and open source software, this community aims to ensure Linux fits your needs and works for you. From troubleshooting to tutorials, practical tips, news and more, all aspects of Linux are warmly welcomed. Join a community of like-minded enthusiasts and professionals driving Linux's ongoing evolution.


Seeking Support?

Community Rules

founded 1 year ago
MODERATORS
 

You can backup your config files before editing them, like this:

cp configbeingedited.conf configbeingedited.conf__orig_datestring

This way, when things break or don't function how you like, you can easily copy the original config file back into position, restoring the original functionality.

you are viewing a single comment's thread
view the rest of the comments
[–] ndotb@programming.dev 4 points 1 year ago (3 children)

Go ahead and graduate to etckeeper if you're targeting /etc

Never knew about this tool, good to know!

[–] ace_garp@lemmy.world 2 points 1 year ago

A good tip for setting up a tool to automate this process.

[–] wackoCamel@lemmy.world 2 points 1 year ago

I tend to make a .bak file before changes. There is nothing worse than fixing one config item only to realize later something else broke and not being sure what it was that changed and no easy way to revert. I'm guilty of having many .bak configs that are poorly named. I hadn't heard of etckeeper before. That looks real handy for me. Thanks for sharing