Majorix said:
Is there a way to let FreeBSD list all the files I have edited manually?
You can check integrity of files with base utility
mktree(8)
Run it first for creating original hashes of files and then run on demand for compare against hashes.
(Good to find which files got changed only)
The best option IMHO it is use
DCVS
You can not only track changes that you did, but also track any changes that was done by software(or hackers).
Beside of that you don't need to propagate similar changes across machines manually since version control systems provide network access for synchronization.
Install
/usr/ports/devel/git for example. Then
CD to directory that you want to track and issue following commands
Code:
git init
git add .
git commit -m "Initial version."
All files and directories recursively will be remembered in repository(inside directory
.git)
When you did some changes to a file(s), issue following commands:
Changed/new files will be added to a repository.
If you'd like to find which files was changed issue command
before "add/commit" and it will show you all changed files
If you'd like to see what exactly was changed to compare with previous version, issue:
Where is
FileName is a file that you want to investigate and you will see side by side old/new changes.
Advantage of using DCVS is that you can check/track history of ALL changes(!!!)
Beside of that you can setup primary repository that you would like to distribute across multiple machines.
All you need to do then on remote computers/VPS/KVM it is
Code:
pkg_add -r git
cd to_dir_that_you_going_to_syncronize
git clone https://Path.To.Your.Repository
At least /etc and /usr/local/etc must be tracked. But you can use it on any important directories to keep track of all files.
So in case if some files will be changed without your knowledge
will show it immediately and give you choice to restore any previous version of changed file(s).
It is a good idea also to run
after each port addition/upgrading to find new changes and if it is ok, remember it as a new tag in file's history by issuing only two command