On чт, 2004-10-21 at 10:59 -0400, David Rea wrote:
> Quoting Rumen Yotov <rumen_yotov@dir.bg>:
> > Hi,
> > Modutils is for 2.4.x kernel-series and module-init-tools is for
> > 2.6.x
> > kernels.
> > Not 100 % sure but on this ML there were reports that
> > module-init-tools
> > works also with 2.4.x kernels (w/o modutils).
> > But to be completely sure could still use 'modutils' and 'emerge
> > module-init-tools -C'.
> > HTH
>
> OK, I did an `emerge -C module-init-tools`. This successfully unmerged
> the package, but now when I do an `emerge -pvuD world` I still get the
> block. Only this time, it's listing the package as "New" to be
> installed.
>
> When I do a `qpkg -q module-init-tools` I get the following:
>
> root@liberty src # qpkg -q module-init-tools
> sys-apps/module-init-tools-3.0-r2
> DEPENDED ON BY:
> sys-kernel/gentoo-sources-2.4.25
> sys-kernel/gentoo-sources-2.4.25-r2
> sys-kernel/gentoo-sources-2.4.25-r3
> sys-kernel/gentoo-sources-2.4.25-r4
> sys-kernel/gentoo-sources-2.4.26-r3
> sys-kernel/gentoo-sources-2.4.26-r9
>
> However, when I do a `qpkg -q modutils` I get this:
>
> root@liberty src # qpkg -q modutils
> sys-apps/modutils-2.4.25 *
> DEPENDED ON BY:
> sys-apps/modutils-2.4.23
> DEPENDED ON BY:
> sys-apps/modutils-2.4.24
> DEPENDED ON BY:
> sys-apps/modutils-2.4.25
> DEPENDED ON BY:
> sys-apps/modutils-2.4.26
> DEPENDED ON BY:
> sys-apps/modutils-2.4.27
> DEPENDED ON BY:
>
> SO - since nothing depends on modutils, but the kernels apparently
> depend on module-init-tools, should I try unmerging modutils instead?
>
> I'm just trying to be very cautious about proceeding; as I mentioned,
> this is my primary workstation and I cannot afford much downtime!
>
> Thanks!
> Dave
>
>
> --
> gentoo-user@gentoo.org mailing list
>
Hi,
For a long (half a year) time working with 2.6-kernel so not recent
experience with 2.4.
Once had a broken system having both modutils and module-init-tools and
what is more interesting this only broke things when modutils (new
version) was compiled AFTER module-init-tools (obviously it thus
overrode some files from module-init-tools - virtual package).
The reverse situation, module-init-tools emerged after modutils worked
w/o problems (for a long time didn't even knew that had to unmerge one).
Only suggest, you go with module-init-tools, but first make a
binary-package of modutils 'quickpkg modutils' just in case.
Or do 'emerge -B module-init-tools' which will only make binary package
of module-init-tools then unmerge modutils and 'emerge -K
module-init-tools' (shouldn't have written this second option :)
HTH
--
Rumen Yotov <rumen_yotov@dir.bg>
