Sep 4, 2004, 9:37 AM
Post #8 of 8
(3422 views)
Permalink
Oh, sorry, I misread your initial post. As someone else replied below,
start by unmerging modutils, then emerge hardened-sources to bring in
module-init-tools.
Dan
On Fri, 3 Sep 2004 20:55:46 -0700, Grant <emailgrant@gmail.com> wrote:
> On Fri, 3 Sep 2004 23:40:13 -0400, Dan Barr <danbarr@gmail.com> wrote:
> > A number of things could have brought module-init-tools in as a
> > dependency. You can try searching through your emerge.log, see what
> > emerge brought it into your system.
> >
> >
>
> 'emerge -pv hardened-sources' looks like this:
>
> B modutils
> N module-init-tools
> N hardened-sources
>
> That means none of them are on my system already right?
>
> - Grant
>
>
>
> >
> >
> > On Fri, 3 Sep 2004 20:38:42 -0700, Grant <emailgrant@gmail.com> wrote:
> > > On Fri, 3 Sep 2004 23:33:24 -0400, Dan Barr <danbarr@gmail.com> wrote:
> > > > module-init-tools is the set of module utilities for the 2.6 kernel
> > > > series. Since hardened-sources is a 2.4 kernel, it requires modutils
> > > > which is for the 2.4 series.
> > > >
> > > > If you're not using a 2.6 kernel at all, go ahead and unmerge
> > > > module-init-tools in favor of modutils.
> > > >
> > > > Dan
> > >
> > > Ok, but how did I end up with module-init-tools on my system? I've
> > > always made the 2.4 choices.
> > >
> > >
> > >
> > > - Grant
>
> --
> gentoo-user@gentoo.org mailing list
>
>
--
gentoo-user@gentoo.org mailing list