From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 3B50A1385B0 for ; Mon, 21 Jan 2013 02:01:48 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CE9E021C0B5; Mon, 21 Jan 2013 02:01:35 +0000 (UTC) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 33E0221C029 for ; Mon, 21 Jan 2013 02:01:33 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id s9so9075447iec.13 for ; Sun, 20 Jan 2013 18:01:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:content-transfer-encoding; bh=5gHxhizwvTLlLhPraevNCnVB5ILxS86lSk7+pqxiCBg=; b=oms3qT6Ww5Bh2eX/kBN2wryUvoP2EMnf6OysrA4gz0PWZgpbatY5AuPAeKE7D01bPV +36wp+9YYBcHwpiFOCKvA2523zjUtcfNtJMCPnu1pWJevzQPjoQSMc01fkGOiGJOsVpt fYY5IAv7VQ1A0jm1EVYyW1G034dNWBlPNrhyLuIwRuq/1NLjbvEQKdUN1UBofUXfjGBq rFoOCFFQgN6ARi5TP/wisfc+EsrPA+QFTsFBXGzRToCksCQjqbnCoaUJyUb58N2nKk2C FeH4jE8glOsxCHEwYJ25y6JAW9Vf9h8Ykrw12C2w67Qs3i48xfi8cefMPodqVkZNTNUg MGGg== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.50.190.199 with SMTP id gs7mr7939860igc.89.1358733693490; Sun, 20 Jan 2013 18:01:33 -0800 (PST) Received: by 10.64.25.111 with HTTP; Sun, 20 Jan 2013 18:01:33 -0800 (PST) In-Reply-To: <20130120194457.70dc468a@fuchsia.remarqs.net> References: <50FAC39E.9070804@gmail.com> <20130120194457.70dc468a@fuchsia.remarqs.net> Date: Sun, 20 Jan 2013 20:01:33 -0600 Message-ID: Subject: Re: [gentoo-user] Re: udev-197-r3 update problem... From: =?UTF-8?B?Q2FuZWsgUGVsw6FleiBWYWxkw6lz?= To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: e9687bef-5861-4b7c-9832-3105e8608264 X-Archives-Hash: 188f53159b2110133fed779866c61bf7 On Sun, Jan 20, 2013 at 7:44 PM, =C2=BBQ=C2=AB wrote: > On Sat, 19 Jan 2013 10:41:07 -0600 > Canek Pel=C3=A1ez Vald=C3=A9s wrote: > >> On Sat, Jan 19, 2013 at 10:02 AM, Jarry 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=3D"nls -common-lisp >> > -static-libs" 429 kB >> > [ebuild N ] dev-libs/libgcrypt-1.5.0-r2 USE=3D"-static-libs" >> > 1,405 kB [ebuild N ] dev-libs/libxslt-1.1.28 USE=3D"crypt >> > -debug -python -static-libs" 3,356 kB >> > [ebuild N ] sys-apps/kmod-12-r1 USE=3D"tools zlib -debug -doc >> > -lzma -static-libs" 1,246 kB >> > [ebuild U ] sys-fs/udev-197-r3 [171-r9] USE=3D"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=3D"-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) >> > >=3Dsys-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 >> > >=3Dsys-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. --=20 Canek Pel=C3=A1ez Vald=C3=A9s Posgrado en Ciencia e Ingenier=C3=ADa de la Computaci=C3=B3n Universidad Nacional Aut=C3=B3noma de M=C3=A9xico