Re: A ipw3945 module for Gentoo 2006.1



Ross Maloney wrote:
Thanks, Gregory, for that reply.

The point that I was making is that emerge was given its freedon to do its thing. A standard Gentoo installation was in place. Such a standard installation DID NOT include the source tree and thus the /usr/src/linux link was not present. Emerge then downloaded the kernel source that was apparently different from the installation (first point). It then created software that was placed in inappropriate placed for the installed system (second point) - which was a standard installation resulting from one of the two installation opitons off the liveCD. That standard installation included the ieee80211 modules that ipw3945 need. The existence of those was overlooked (third point).

I can see what emerge has done and why it has done it. But there is a difference between non-perfect, and sloppy software engineering. Although I believe that Gentoo has a lot to be said for it, I am less than impressed with emerge and the associated portage. This is an instance were it has not worked.

Ross

Point one: A "standard Gentoo installation" requires that you install a kernel using kernel sources - step seven in the installation handbook.
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml

Point two: Emerge assumes that the kernel sources are at /usr/src/linux
and bases the installation point of modules on the version of the kernel
at that location. Emerge could possibly be more intelligent in looking
for the current kernel sources but that could also make building a
kernel off of new sources more difficult. Its easier to assume that you
are following the directory setup outlined in the installation handbook
and other places.

Point three: When installing modules for a particular kernel version,
the existence of modules for other versions are ignored. No way
around this one.

Doug
.



Relevant Pages

  • Re: A ipw3945 module for Gentoo 2006.1
    ... That was the root of my problems - the LiveCD resulted in an installation that was incomplete for kernel subsequent usage. ... I agree with the Gentoo philosopy of a minimal installation which can then be configured or built upon in whatever way is desired. ... Emerge then downloaded the kernel source that was apparently different from the installation. ... A "standard Gentoo installation" requires that you install a kernel using kernel sources - step seven in the installation handbook. ...
    (comp.os.linux.misc)
  • Re: A ipw3945 module for Gentoo 2006.1
    ... This comes down to what constitutes a "standard" Gentoo installation. ... That was the root of my problems - the LiveCD resulted in an installation that was incomplete for kernel subsequent usage. ... A "standard Gentoo installation" requires that you install a kernel using kernel sources - step seven in the installation handbook. ...
    (comp.os.linux.misc)
  • Re: A ipw3945 module for Gentoo 2006.1
    ... Such a standard installation DID NOT include the source tree and thus the /usr/src/linux link was not present. ... Emerge then downloaded the kernel source that was apparently different from the installation. ... Although I believe that Gentoo has a lot to be said for it, I am less than impressed with emerge and the associated portage. ...
    (comp.os.linux.misc)
  • Re: A ipw3945 module for Gentoo 2006.1
    ... I remember reading somewhere in the documentation that a "networkless" installation does not install a kernel source tree. ... The kernel sources that it grabbed were not those of the kernel that had been installed using the networkless installation off the LiveCD - r5 as opposed to r7. ... Emerge then downloaded the kernel source that was apparently different from the installation. ...
    (comp.os.linux.misc)
  • Re: Encounter: rdaInit.tcl failed
    ... guess an emerge -uD world would break the installation. ... missing a dependency somewhere.... ...
    (comp.cad.cadence)