| 1 |
On Sun, Jan 20, 2013 at 7:44 PM, »Q« <boxcars@×××.net> wrote: |
| 2 |
> On Sat, 19 Jan 2013 10:41:07 -0600 |
| 3 |
> Canek Peláez Valdés <caneko@×××××.com> wrote: |
| 4 |
> |
| 5 |
>> On Sat, Jan 19, 2013 at 10:02 AM, Jarry <mr.jarry@×××××.com> wrote: |
| 6 |
>> > Hi Gentoo-users, |
| 7 |
>> > |
| 8 |
>> > I'm just in the process of updating my nearly identical servers. |
| 9 |
>> > Some of them I updated without any problem. "Unfortunatelly", |
| 10 |
>> > right now new udev-197-r3 went stable, and so those servers |
| 11 |
>> > which I synced with portage-tree later want to pull udev-197, |
| 12 |
>> > and give this error: |
| 13 |
>> > |
| 14 |
>> > --------------------------- |
| 15 |
>> > vs1-sys ~ # emerge --ask --update --deep --newuse --verbose world |
| 16 |
>> > |
| 17 |
>> > These are the packages that would be merged, in order: |
| 18 |
>> > |
| 19 |
>> > Calculating dependencies... done! |
| 20 |
>> > [ebuild N ] dev-util/gperf-3.0.4 961 kB |
| 21 |
>> > [ebuild N ] dev-libs/libgpg-error-1.10 USE="nls -common-lisp |
| 22 |
>> > -static-libs" 429 kB |
| 23 |
>> > [ebuild N ] dev-libs/libgcrypt-1.5.0-r2 USE="-static-libs" |
| 24 |
>> > 1,405 kB [ebuild N ] dev-libs/libxslt-1.1.28 USE="crypt |
| 25 |
>> > -debug -python -static-libs" 3,356 kB |
| 26 |
>> > [ebuild N ] sys-apps/kmod-12-r1 USE="tools zlib -debug -doc |
| 27 |
>> > -lzma -static-libs" 1,246 kB |
| 28 |
>> > [ebuild U ] sys-fs/udev-197-r3 [171-r9] USE="acl%* kmod%* |
| 29 |
>> > openrc%* -doc% -gudev -hwdb -introspection -keymap (-selinux) |
| 30 |
>> > -static-libs% (-action_modeswitch%) (-build%) (-debug%) (-edd%) |
| 31 |
>> > (-extras%) (-floppy%) (-rule_generator%*) (-test%)" 2,008 kB |
| 32 |
>> > [ebuild U ] virtual/udev-197 [171] USE="-gudev -hwdb |
| 33 |
>> > -introspection -keymap (-selinux) -static-libs" 0 kB |
| 34 |
>> > [ebuild N ] sys-fs/udev-init-scripts-19 5 kB |
| 35 |
>> > [blocks B ] sys-apps/kmod ("sys-apps/kmod" is blocking |
| 36 |
>> > sys-apps/module-init-tools-3.16-r2) |
| 37 |
>> > [blocks B ] sys-apps/module-init-tools |
| 38 |
>> > ("sys-apps/module-init-tools" is blocking sys-apps/kmod-12-r1) |
| 39 |
>> > |
| 40 |
>> > Total: 8 packages (2 upgrades, 6 new), Size of downloads: 9,407 kB |
| 41 |
>> > Conflict: 2 blocks (2 unsatisfied) |
| 42 |
>> > |
| 43 |
>> > * Error: The above package list contains packages which cannot be |
| 44 |
>> > * installed at the same time on the same system. |
| 45 |
>> > |
| 46 |
>> > (sys-apps/kmod-12-r1::gentoo, ebuild scheduled for merge) pulled |
| 47 |
>> > in by sys-apps/kmod[tools] required by (virtual/modutils-0::gentoo, |
| 48 |
>> > installed) |
| 49 |
>> > >=sys-apps/kmod-12 required by (sys-fs/udev-197-r3::gentoo, |
| 50 |
>> > >ebuild |
| 51 |
>> > scheduled for merge) |
| 52 |
>> > |
| 53 |
>> > (sys-apps/module-init-tools-3.16-r2::gentoo, installed) pulled in |
| 54 |
>> > by |
| 55 |
>> > >=sys-apps/module-init-tools-3.2 required by |
| 56 |
>> > (virtual/modutils-0::gentoo, installed) |
| 57 |
>> > |
| 58 |
>> > ------------------- |
| 59 |
>> > |
| 60 |
>> > So how can I fix this mess? I masked sys-fs/udev-197-r3, |
| 61 |
>> > now portage does not complain, but it is just temporary |
| 62 |
>> > solution... |
| 63 |
>> |
| 64 |
>> try: |
| 65 |
>> |
| 66 |
>> emerge -Cv sys-apps/module-init-tools |
| 67 |
>> emerge -1v sys-apps/kmod |
| 68 |
>> |
| 69 |
>> and then try to update world again. kmod is a drop-in replacement for |
| 70 |
>> module-init-tools, and it's what is used by new versions of udev. You |
| 71 |
>> probably will need to keyword kmod. |
| 72 |
> |
| 73 |
> adev-197 has a kmod useflag, on by default (at least in my profile). |
| 74 |
> Disabling it lets you keep module-init-tools. I noticed because I am |
| 75 |
> one of those risk-takers who has USE -* , and now I'm wondering what |
| 76 |
> the benefits of kmod would be for me (and/or disadvantages). |
| 77 |
> |
| 78 |
> If this has already been discussed here, my apologies. I try to pay |
| 79 |
> attention, but, well, you know what all udev threads are like. ;) |
| 80 |
|
| 81 |
kmod, if built with the tools USE flag (which is enabled by default), |
| 82 |
works as a drop-in replacement for module-init-tool. To the users of |
| 83 |
OpenRC (AFAIK), there is really no difference between the two of them, |
| 84 |
except perhaps that kmod is actively developed and several distros are |
| 85 |
moving to it, so it will probably (me thinks) be the one the kernel |
| 86 |
will explicitly support in the future. |
| 87 |
|
| 88 |
For systemd users kmod makes the boot time even faster, since kmod is |
| 89 |
a library and it allows to do module related operations from C, |
| 90 |
instead of calling (and therefore forking) modprobe or other programs. |
| 91 |
|
| 92 |
Outside of that, as I said, I don't think there is any significant |
| 93 |
difference between kmod and module-init-tools; as the README from kmod |
| 94 |
says: |
| 95 |
|
| 96 |
"The aim is to be compatible with tools, configurations and indexes |
| 97 |
from module-init-tools project." |
| 98 |
|
| 99 |
Hope it helps. |
| 100 |
|
| 101 |
Regards. |
| 102 |
-- |
| 103 |
Canek Peláez Valdés |
| 104 |
Posgrado en Ciencia e Ingeniería de la Computación |
| 105 |
Universidad Nacional Autónoma de México |
Archives