this is not really a project yet, just an idea with some thoughts about its implementation.
The typical problem I have in mind is the following: At some point a user tweaks some system settings by editing some configuration files. The tweak works nicely and he forgets what he has done. But then, after some years, something breaks. He goes to the forums, describes the symptoms but nobody can really figure out what is going on. After a lot of troubleshooting it turns out that the change which he made a few years ago and completely forgot about was the reason for the breakage.
Preliminary thoughts on how to deal with such problems: It would be great to have a complete list of system modifications specifically done by the user (as opposed to what is being done during package updates by pacman and is known do the Manjaro devs). This way one could scroll through this protocol and possibly find inspiration when searching for unexplainable problems. Of course it is hard to get a complete list. But I think, a majority of such system modifications can be found by recording any bash command which involves the usage of sudo (people who prefer su are on their own there) and some path outside of /home.
Proposed solution: An alias for sudo which calls sudo the usual way and echoes some information to some plain text journal file: date&time, user who is running sudo, pathes which are present in the command and (just in case) the complete command. Possibly also a diff between old and new version of the file being edited. Details on how to organize the information in a readable way are to be discussed. A GUI with possibility to filter w.r.t. date, path etc would be a plus but considerably more effort.
Questions: Is it a good idea in terms of usability and in terms of security? If so, does something similar exist already?
Thanks for reading,