Bug 71264 - a section on installing hotplug needs to be updated with the coldplug information
|
Bug#:
71264
|
Product: Docs-user
|
Version: n/a
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: major
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: swift@gentoo.org
|
Reported By: chris.zapart@yahoo.co.uk
|
|
Component: Handbook
|
|
|
URL:
|
|
Summary: a section on installing hotplug needs to be updated with the coldplug information
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2004-11-15 02:22 0000
|
Following the recent changes made to the hotplug scripts (the removal of the
init.d hotplug functionality) the section 7d in the installation handbook needs
to be updated with information about installing coldplug too.
For example:
Immediately after configuring and compiling the kernel the manual tells you to
install hotplug:
------------------------------------------------------------------------------------------------------------------
Now, let's perform one more step to get our system to be more like the Live CD
-- let's emerge hotplug. While the initrd autodetects hardware that is needed
to boot your system, hotplug autodetects everything else. To emerge and
enable hotplug, type the following:
Code Listing 19: Emerging and enabling hotplug
# emerge hotplug
# rc-update add hotplug default
------------------------------------------------------------------------------------------------------------------
What really needs to be done is the following:
emerge hotplug
emerge coldplug
rc-update add coldplug boot
This will install both hotplug and coldplug packages and then put the coldplug
package into the init.d script to be run at boot time (before the default run
level). The new coldplug package takes over the tasks that were previously
done by the hotplug script when booting.
I am not sure what are the ebuild dependencies for the coldplug package.
Perhaps emerging coldplug would automatically emerge hotplug too. But in any
case it is now the coldplug package that needs to be added to the boot
runlevel, not hotplug which does nothing at boot after the recent changes.
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
I'm going to do a s/hotplug/coldplug/ since that's what's most important. I
don't think we really ought to list hotplug as well. Perhaps we should, but the
hotplug->coldplug is a first objective.
Done in CVS. If hotplug is necessary during installation (I don't think it is
but I hardly use it), please reopen.
Edward,
You're right. In fact I've added hotplug back to the default run-level on my system.
And in the boot runlevel the new coldplug scripts take care of loading any required kernel modules like e1000 for networking etc.
I think you only need to emerge coldplug (without emerging hotplug) because as part of its dependencies coldplug will install hotplug anyway. Then you just need to add coldbplug to the boot and hotplug to the default runlevel as per your comments.
The hotplug-part is optional, but I'll bite anyway :)
The 2004.3 won't be changed though, that's release-specific and at the 2004.3 release there was no coldplug (hotplug did both).
Updated in CVS.