The handbook says to emerge coldplug, but it is masked ~amd64 (at least it is when trying to do a non-connected installation). No instructions are provided to a new user during installation on how to deal with this (i.e. ACCEPT_KEYWORDS). 1. Is coldplug supposed to be masked? 2. Is a new user supposed to use ACCEPT_KEYWORDS? 3. Should document be updated? Reproducible: Always Steps to Reproduce: 1. emerge coldplug 2. 3. Actual Results: Needed to do this: ACCEPT_KEYWORDS="~amd64" emerge coldplug emerge info Portage 2.0.51-r3 (default-linux/amd64/2004.3, gcc-3.4.3, glibc-2.3.4.20040808-r1, 2.6.9-gentoo-r9 x86_64) ================================================================= System uname: 2.6.9-gentoo-r9 x86_64 AMD Athlon(tm) 64 Processor 3400+ Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.90.0.1.1-r3 Headers: sys-kernel/linux26-headers-2.6.8.1-r1 Libtools: sys-devel/libtool-1.5.2-r7 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CFLAGS="-march=k8 -pipe -fomit-frame-pointer -O2" CHOST="x86_64-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control"CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=k8 -pipe -fomit-frame-pointer -O2" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox" GENTOO_MIRRORS="http://gentoo.osuosl.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X acpi alsa berkdb bitmap-fonts cdr crypt cups esd f77 fam fortran gif gnome gpm gstreamer gtk imlib ipv6 jp2 jpeg ldap lzw lzw-tiff mozilla multilib ncurses nls opengl oss pam perl png python readline ssl tcpd tiff truetype usb userlocales xml xml2 xmms xpm xrandr xv zlib"
This is somewhat a documentation problem. At the time when the release was finalized, coldplug was not marked stable on amd64/x86. In fact, the hotplug on the LiveCD does the same as coldplug does now. It seems as if the documentation has been updated to reflect the current state of the tree and not the state of the tree as it was at release. My tip for now, use the handbook on the CD, not online. My tip for the docs-team guys: Make a note that if you're doing a networkless install, that you should use hotplug and not coldplug.
It is also an issue for x86. Unmasking does not help, because the dependent hotplug package is too old in the 2004.3-r1 LiveCD. I believe it is impossible to emerge the coldplug networklessly in this case. Unmasking also wants to install unstable versions of other dependent packages. My workaround: 1. download the hotplug-2004_09_23.tar.gz and its md5 checksum (possibly using other Internet enabled computer or OS) 2. copy the files into /usr/portage/distfiles on your disk partition (i.e. /mnt/gentoo/usr/portage/distfiles after LiveCD booting) 3. emerge pciutils 4. emerge usbutils 5. emerge hotplug-base 6. ACCEPT_KEYWORDS="~x86" emerge coldplug
Actually, it is more a case of you NOT using coldplug in a non-networked install. The documentation has been changed since 2004.3 was released. The documentation on the LiveCD is correct, the "current" documentation is not. Release Engineering and the Documentation Team are currently working on possible solutions for this.
I've updated the docs to reflect the situation.
So, if I networked my system to complete my installation of 2004.3-r1 and installed coldplug on an amd64 system, do I continue to use it or should I unemerge it and emerge hotplug. If I should unemerge, what should I watch out for? My system seems to ge working OK right now.
*** Bug 76430 has been marked as a duplicate of this bug. ***
If you emerge sync at all, then you should use coldplug. If you never sync, then you should use hotplug.
BTW, with the separation of installation instructions, the 2004.3 II uses hotplug, the current II uses coldplug. The 2004.3 II also inform the user about this change (and the kernel change) at the end of the installation.
Very nice...
This should be fixed in 2005.0
