Restricting automatic kernel-module loading
Restricting automatic kernel-module loading
Posted Dec 4, 2017 21:53 UTC (Mon) by gutschke (subscriber, #27910)In reply to: Restricting automatic kernel-module loading by simcop2387
Parent article: Restricting automatic kernel-module loading
That's exactly right. It would be a manually maintained field. It doesn't *technically* require that this is the last time the source has changed. But it would be the last time a maintainer re-affirmed that the module is still actively maintained. Frequently, that would go hand-in-hand with making source code changes. But it doesn't have to.
Similarly, it is possible for somebody to change the source code (e.g. to make adjustments for kernel-wide API changes) without asserting the responsibility of a full-time committed maintainer. In that case, they would not bump up the version number.
The important part is that this number would never be changed automatically. It is always a conscious decision by a human developer.
