On Sun, Jan 20, 2013 at 7:44 PM, »Q« <boxc...@gmx.net> wrote:
> On Sat, 19 Jan 2013 10:41:07 -0600
> Canek Peláez Valdés <can...@gmail.com> wrote:
>
>> On Sat, Jan 19, 2013 at 10:02 AM, Jarry <mr.ja...@gmail.com> wrote:
>> > Hi Gentoo-users,
>> >
>> > I'm just in the process of updating my nearly identical servers.
>> > Some of them I updated without any problem. "Unfortunatelly",
>> > right now new udev-197-r3 went stable, and so those servers
>> > which I synced with portage-tree later want to pull udev-197,
>> > and give this error:
>> >
>> > ---------------------------
>> > vs1-sys ~ # emerge --ask --update --deep --newuse --verbose world
>> >
>> > These are the packages that would be merged, in order:
>> >
>> > Calculating dependencies... done!
>> > [ebuild N ] dev-util/gperf-3.0.4 961 kB
>> > [ebuild N ] dev-libs/libgpg-error-1.10 USE="nls -common-lisp
>> > -static-libs" 429 kB
>> > [ebuild N ] dev-libs/libgcrypt-1.5.0-r2 USE="-static-libs"
>> > 1,405 kB [ebuild N ] dev-libs/libxslt-1.1.28 USE="crypt
>> > -debug -python -static-libs" 3,356 kB
>> > [ebuild N ] sys-apps/kmod-12-r1 USE="tools zlib -debug -doc
>> > -lzma -static-libs" 1,246 kB
>> > [ebuild U ] sys-fs/udev-197-r3 [171-r9] USE="acl%* kmod%*
>> > openrc%* -doc% -gudev -hwdb -introspection -keymap (-selinux)
>> > -static-libs% (-action_modeswitch%) (-build%) (-debug%) (-edd%)
>> > (-extras%) (-floppy%) (-rule_generator%*) (-test%)" 2,008 kB
>> > [ebuild U ] virtual/udev-197 [171] USE="-gudev -hwdb
>> > -introspection -keymap (-selinux) -static-libs" 0 kB
>> > [ebuild N ] sys-fs/udev-init-scripts-19 5 kB
>> > [blocks B ] sys-apps/kmod ("sys-apps/kmod" is blocking
>> > sys-apps/module-init-tools-3.16-r2)
>> > [blocks B ] sys-apps/module-init-tools
>> > ("sys-apps/module-init-tools" is blocking sys-apps/kmod-12-r1)
>> >
>> > Total: 8 packages (2 upgrades, 6 new), Size of downloads: 9,407 kB
>> > Conflict: 2 blocks (2 unsatisfied)
>> >
>> > * Error: The above package list contains packages which cannot be
>> > * installed at the same time on the same system.
>> >
>> > (sys-apps/kmod-12-r1::gentoo, ebuild scheduled for merge) pulled
>> > in by sys-apps/kmod[tools] required by (virtual/modutils-0::gentoo,
>> > installed)
>> > >=sys-apps/kmod-12 required by (sys-fs/udev-197-r3::gentoo,
>> > >ebuild
>> > scheduled for merge)
>> >
>> > (sys-apps/module-init-tools-3.16-r2::gentoo, installed) pulled in
>> > by
>> > >=sys-apps/module-init-tools-3.2 required by
>> > (virtual/modutils-0::gentoo, installed)
>> >
>> > -------------------
>> >
>> > So how can I fix this mess? I masked sys-fs/udev-197-r3,
>> > now portage does not complain, but it is just temporary
>> > solution...
>>
>> try:
>>
>> emerge -Cv sys-apps/module-init-tools
>> emerge -1v sys-apps/kmod
>>
>> and then try to update world again. kmod is a drop-in replacement for
>> module-init-tools, and it's what is used by new versions of udev. You
>> probably will need to keyword kmod.
>
> adev-197 has a kmod useflag, on by default (at least in my profile).
> Disabling it lets you keep module-init-tools. I noticed because I am
> one of those risk-takers who has USE -* , and now I'm wondering what
> the benefits of kmod would be for me (and/or disadvantages).
>
> If this has already been discussed here, my apologies. I try to pay
> attention, but, well, you know what all udev threads are like. ;)
kmod, if built with the tools USE flag (which is enabled by default),
works as a drop-in replacement for module-init-tool. To the users of
OpenRC (AFAIK), there is really no difference between the two of them,
except perhaps that kmod is actively developed and several distros are
moving to it, so it will probably (me thinks) be the one the kernel
will explicitly support in the future.
For systemd users kmod makes the boot time even faster, since kmod is
a library and it allows to do module related operations from C,
instead of calling (and therefore forking) modprobe or other programs.
Outside of that, as I said, I don't think there is any significant
difference between kmod and module-init-tools; as the README from kmod
says:
"The aim is to be compatible with tools, configurations and indexes
from module-init-tools project."
Hope it helps.
Regards.
--
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México
