On Wed, Feb 06, 2013 at 01:16:11AM +0100, Joerg Sonnenberger wrote: > On Tue, Feb 05, 2013 at 10:25:23AM +0000, David Holland wrote: > > On Mon, Feb 04, 2013 at 09:39:04PM +0100, Joerg Sonnenberger wrote: > > > we have quite a few tools in base that still require KVM or optionally > > > support it. Removing all tools that require KVM for operation (and > > > therefore setgid) is one of the open goals. It would be nice if that > > > doesn't require adding lots of duplicate code. For that, a decision is > > > required what programs are required for post-mortem analysis (i.e. > > > debugging kernel dumps) and limit dual-KVM/sysctl code paths to that. > > > > ISTM that there should be one library (probably not the libkvm we > > currently have) that does both things transparently. That, or sysctl > > emulation for dump images. > > That still requires duplicate code, so it doesn't change the question of > what such code is needed for.
Er wut? For any particular piece of data there are two rather different ways to get it, but I don't see what's duplicative about this. -- David A. Holland [email protected]
