Re: The future of m-a and dkms
On Wed, 16 Feb 2011 00:13:07 +0000, Ben Hutchings
>On Wed, 2011-02-16 at 00:44 +0100, Iustin Pop wrote:
>> On Mon, Feb 14, 2011 at 02:43:23PM +0000, Ben Hutchings wrote:
>> > On Mon, Feb 14, 2011 at 12:19:37PM +0100, Klaus Ethgen wrote:
>> > > With m-a it was and is possible to create nice debian packages for
>> > > custom modules which can be installed on all systems getting all the
>> > > same modules. With dkms that is not possible. More over you need to have
>> > > a full gcc suite on all servers where you have custom modules. That is
>> > > not acceptable.
>> > [...]
>> > This is not true. You can use 'dkms mkdeb' to build module packages
>> > elsewhere.
>> As others have said in this thread (and from my experience too), you
>> can't use dkms mkdeb to build and install separate packages for two
>> kernel versions but same module. That is because it uses only the
>> package name & version in the module paths, hence it doesn't support
>> nice upgrades.
>But you can build a single package that contains binaries for multiple
So I'll have to build packages for each migration type that I want to
do and replace the modules _before_ the actual kernel update,
exchanging the modules for the currently running kernel in this
This makes my toes curl. Please, Debian, don't force that on me.
-------------------------------------- !! No courtesy copies, please !! -----
Marc Haber | " Questions are the | Mailadresse im Header
Mannheim, Germany | Beginning of Wisdom " | http://www.zugschlus.de/
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834