Description:
Provide the ability to log all configuration changes done via YaST.
Additionally, in this mode an admin would be prompted to document what
was the nature/purpose of the change as the module is being closed,
akin to commit messages in a versioning system.

Documentation Impact:
The new log file needs to be documentated in admin guide.

Discussion:
#1: Federico Lucifredi(flucifredi@xxxxxxxxxx) (2008-04-30 15:27:04)
note fate 303688 related: packaging CFT. I am not sure CFT is the right
way to provide this functionality, but a consideration is that an admin
using CFT will probably log both manual-editing and YaST-driven conf
changes via the same tool.

#2: Stanislav Visnovsky(visnov@xxxxxxxxxx) (2008-06-03 12:40:41)
Duncan, Jiri, this might be an architectural change, please, look into
this. Also, we might need to define scope of which changes we are able
to track.

#3: Jiri Srain(jsrain@xxxxxxxxxx) (2008-07-07 10:45:35)
Martin, please, have a look at possibilities to record all changes and
suggest an infrastructure.
Federico, we will hardly be able to make all modules record all the
changes they do. Could you, please, give us some priorities for SLE11?

#4: Martin Vidner(mvidner@xxxxxxxxxx) (2008-07-08 11:44:54)
This looks like a superset of feature 100386. Note that that one was
downgraded because it is large (it requires touching all YaST
modules).

#5: Stanislav Visnovsky(visnov@xxxxxxxxxx) (2008-07-08 12:08:56) (reply
to #4)
Please, look into enabling of the stuff, not covering all YaST
modules.