SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have posted a thread sometime ago about 188.8.131.52 hang at /etc/rc.d/rc.hotplug while boot-up
In actually case it didn't hang. It just seems to hang. It takes EXTREMLY LONG TIME to get pass the /etc/rc.d/rc.hotplug. I discovered this because there was a blackout which outlast my UPS. After I return to my comp after a few days. It manage to boot-up successfully.
A comparison with 2.6.7, 184.108.40.206 is eternity.
I used the same config file from 2.6.7 to compile 220.127.116.11. And also reconfigure it from scratch with the same results.
I agree with gbonvehi about loading modules in rc.modules.
Compile your kernel with hotplugging support on (but not PCI hotplugging - unless you know for sure you can hot swap PCI cards ). It also very useful to compile your USB controller and the HID driver directly into your kernel, because you always want to be able to use your USB keyboard and mouse to talk to your machine. Not so important if you have PS/2 ports and devices available as well.
Maybe I'm wrong but I think hotplug is a misnomer for rc.hotplug and /etc/hotplug. At the least it is wrong that the /etc/hotplug/*.rc scripts refer to recovering "hotplug" events that couldn't be handled earlier in the boot process. Now, detecting a PCI device that was inserted before power on is not hotplugging! PCI is not hot pluggable on 99.9999% of computers -- it requires specialist equipment. You can't just insert a device into an ordinary PCI slot on a running machine
I think the main job of the rc.hotplug is to pick up on lost plug and play (not hotplug) events during boot up, which couldn't be handled previously in the boot process. USB hotplugging (connecting and disconnecting devices on a running machine) works without this script, at least as long as the drivers are already running.
So isn't rc.hotplug just automatic hardware detection that gets your system up and running, but can be discarded if you optimise your kernel and startup scripts? Like Gentoo (genkern vs manual kernel compile)? Or does it do something else which carboncopy and myself should keep in mind?
Last edited by worldwiderob; 09-30-2004 at 03:50 PM.