From mboxrd@z Thu Jan  1 00:00:00 1970
From: Robby Workman <robby@rlworkman.net>
Date: Thu, 12 Jan 2012 14:27:03 +0000
Subject: Re: udev 177 and kmod3
Message-Id: <20120112082703.2db1335a@liberty.rlwhome.lan>
List-Id: <linux-hotplug.vger.kernel.org>
References: <4F0E7F79.9000503@gmail.com>
In-Reply-To: <4F0E7F79.9000503@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: linux-hotplug@vger.kernel.org

On Thu, 12 Jan 2012 10:56:31 -0200
Lucas De Marchi <lucas.demarchi@profusion.mobi> wrote:

> Hi Bruce,
> 
> On Thu, Jan 12, 2012 at 4:36 AM, Bruce Dubbs <bruce.dubbs@gmail.com>
> wrote:
> > udev-177 appears to require kmod3, yet the kmod3 announcement says:
> >
> > "I'd not say distros could start shipping
> > kmod instead of module-init-tools yet."
> >
> > There appears to be a miscommunication here.
> 
> 
> There isn't.
> 
> If udev doesn't care about kmod's man pages, then it's good to start
> using libkmod. For the udev's use cases, libkmod is pretty complete.
> It can be installed in parallel to module-init-tools too if distros
> don't seem confident to make a step further and replace it.
> 
> So far Archlinux seems to be the first one. kmod is in their testing
> repo and they helped us a lot to fix some bugs. Then I'd say kmod 4
> will be ready enough for distros.


Agreed on that.  We don't have it in Slackware yet, but I've been
running it locally since v2 (and fully replaced m-i-t since v3),
and aside from a few minor issues (that have mostly been fixed),
it's fine.  

-RW