On Thu, Oct 09, 2008 at 12:29:03PM +0200, Joerg Barfurth wrote: > Bart Blanquart schrieb: > > Now, the goal is to avoid the need to deal with modified pam.conf or > > equivalent files when upgrading a system (or patching or similar). > > > > The easiest way to go about that seems fairly simple: > > > > One aspect that seems to be unaccounted for in much of this discussion > is that there are three sources of modifications to PAM configuration: > > 1. System updates and upgrades > 2. Customer policy > 3. Layered/ISV software
We've been discussing exactly that in some sub-threads.
